Core Apps Test Review
Let's review each of the core apps and there current status in regards to tests.
Are more tests needed?
Do we have 100% feature coverage?
Are new tests being added as features are added?
Do the tests run and pass reliably?
Blueprint information
- Status:
- Not started
- Approver:
- Jono Bacon
- Priority:
- Undefined
- Drafter:
- Nicholas Skaggs
- Direction:
- Approved
- Assignee:
- Nicholas Skaggs
- Definition:
- New
- Series goal:
- Accepted for trusty
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Let's review each of the core apps and there current status in regards to tests.
Are more tests needed?
Do we have 100% feature coverage?
how do we determine coverage?
At leats 1 test per user story
How do we define a user story?
something that gives value to the user.
A user story can be split in more than one test.
if no design document, then ?
4 or 5 core apps do have some design document
Some features don't give direct value to the user, like changing a config setting.
We can test them with QtTest or autopilot, depending on how hard to write and maintain the code would be.
- needs-autopilot
Are new tests being added as features are added?
- Test addition/
Do the tests run and pass reliably?
we don't know why tings fail when they fail; we don't keep track
we often pursue quick fixes for failures
tests should be written with failures in mind so failures are more obvious
can the CI team provide data or be masters of the data?
Are the test suites compatible with both python 2 *and* python 3?
If not, how can we make that happen in a timely manner?
Need to access only local sources for data!
ubuntu-
Leo wants to refactor
remember to mockup for network issues
2 tests need to be re-enabled and tested (swipe to delete emulator)
test_
test_
missing tests
test to swipe for different hours in the day
ubuntu-
all good :-)
ubuntu-
forces us to use internet resources which can cause failures
https:/
needs smaller tests, a bit of refactoring
ubuntu-
remove patching home
refactor to use new folder
ubuntu-
refactor to only use local sources
land mp's
https:/
https:/
alarm tests
UI alarm test in autopilot
lower level tests for push notifications
ubuntu-
some tests better as unit tests, but they all work and features covered
dropping-
Good, no code changes, tests rock solid
music-app-autopilot 2013/11/20 14:48 8 7 1 0 0 87.5%
shuffle implementation and tests have been an issue
Needs tests for interfacing with Aritsts, Albums, Songs tabs
Needs tests for each tab to add an item to a playlist or the queue
Needs tests to create and modify playlists
Needs tests for swipe to delete of playlist items and queue items
calendar-
3 mp's need to land / merge.
once landed all features should have tests
https:/
https:/
ubuntu-
sudokutouchgame
not in public jenkins view
can we add?
stock-ticker-
not in public jenkins view
can we add?
https:/
https:/
Work Items
Work items:
[nskaggs] add work items for above failures ^^!: DONE
[elopio] get the weather app to 100% green.: DONE
[popey] Add table to wiki page for <expand for all coreapp> listing features, implementation status and test coverage: TODO
[nskaggs] Fill in feature tables with current test coverage: TODO
Run test suite for <expand for all coreapp> using python 3, file bugs for any errors that are different from python 2: DONE
[elopio] make sure the SDK emulators work in python 2 and python 3.: TODO
[nskaggs] Make sure all core apps have MP test passing enforced before landing in trunk: DONE
[thomir-
[thomir-
Dependency tree
* Blueprints in grey have been implemented.