#345 Cleanup unittests
Closed: MIGRATED a year ago by nikromen. Opened 5 years ago by clime.

Our unittests would deserve some revision and clean-up. Especially backend ones when half of them is disabled. Frontend ones as well. We should keep our unittests in order.

Edit by @praiskup, we should:

  1. we should make sure that all test files are observable by pytest
  2. make sure that there's no skipped test on backend (fix or drop the test)
  3. we should enable coverage in run_tests.sh
  4. we should make sure that all the run_tests.sh scripts have the same semantics, e.g. that it accepts -k test_name option
  5. maybe we could have only one run_tests.sh script and symlink it, to avoid duplication

This is a neverending task without a clear goal to achieve.

Metadata Update from @msuchy:
- Issue status updated to: Closed (was: Open)

5 years ago

Why did you close this task? Backend unittests need revision and this is an issue filed for this purpose.

Metadata Update from @clime:
- Issue status updated to: Open (was: Closed)

5 years ago

IMHO because this issue is not specific enough. How do we know, when it is resolved? I agree with re-opening it, but some checklist describing what needs to be done is necessary.

Metadata Update from @praiskup:
- Issue tagged with: code-cleanup

5 years ago

I updated the initial description. The first point should be resolved in #1007.

Commit b353d11 relates to this ticket

Commit 45256db relates to this ticket

Commit 78434bb relates to this ticket

Commit a0eaf42 relates to this ticket

Commit 98d5dba relates to this ticket

Commit 7e85440 relates to this ticket

Commit 1038e6f relates to this ticket

Metadata Update from @nikromen:
- Issue close_status updated to: MIGRATED
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #1150 Merged 4 years ago