Soyuz Test-Suite baseline
Bug #2017 reported by
Celso Providelo
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
We need to extend the test-suite to cover Soyuz parts (pages, database and view clasess).
Steve suggested the following plan:
(13:24:25) SteveA: - every page has a page test that shows at least that it gives the correct HTTP response (200 usually)
(13:25:11) SteveA: - every database class (Foo or FooSet) has a test that shows it can be imported, got from the database, and trivially used in some way
(13:25:33) SteveA: - every view class has a test that shows it can be imported
Revision history for this message
| Diogo Matsubara (matsubara) wrote | #1 |
| Changed in soyuz: | |
| status: | Unconfirmed → Needs Info |
Revision history for this message
| Celso Providelo (cprov) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in launchpad: | |
| status: | Invalid → Confirmed |
| assignee: | nobody → emmanuel (emmanuel52759) |
| information type: | Public → Public Security |
| Changed in launchpad: | |
| status: | Confirmed → Invalid |
| assignee: | emmanuel (emmanuel52759) → nobody |
| information type: | Public Security → Public |
To post a comment you must log in.
How's the test coverage on soyuz? I think this can be closed because of the 'no-code without tests' policy. Am I right?