AUS:Tests: Difference between revisions

Jump to navigation Jump to search
259 bytes added ,  6 September 2006
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
= Questions =
= Short-term =
* Do we start over?
* Modify existing sanity scripts to be automated and configurable to improve coverage for 1.5.0.7 release
* What can we move over from the bash tests?
* Existing release tests will be used for .mar patch file application and end-to-end verification
* Do we just keep things in bash and wrap the new stuff?
* Where should we plug in the existing updates.cfg?
* How would we piggyback the actual update application onto a new set of .py tests?  Doable?
* CVS structure?  SVN? :)
aus/tests/
    cases.html
    fixtures.py
    methods.py
    *.sh?


= TODO =
== TODO ==
* Generate schema so we can easily dump build data from snippet repository
* Create migration script to get build data imported into database
* Use data to generate URIs and all available combinations
* Create ability to run tests against either manually set controls or previous versions of AUS -- use database to run "focused" tests (say, testing a specific channel / product / version, for example)
 
= Long-term =
* Decide how we will integrate the existing release tests with pyFit-based tests
* Decide how we will integrate the existing release tests with pyFit-based tests
* Start setting up very simple tests and utilize pyFit to store our 'expected results'
* Start setting up very simple tests and utilize pyFit to store our 'expected results'
3,035

edits

Navigation menu