The following page contains notes from Monday Rx Project meetings:
and the PowerPoint presentation on the architecture is attached to this page.
High Level Requirements and Requested Features
For the first phase,
- Functionality of current player
- Functionality of current server
- Runs on Windows 7 or Linux
- Demonstrate the primary use case.
The features in the following list are not currently supported by DvrExerciser. Many may be added without updates to Rx. Later phases will add these features. The point is that the design of Rx should not make it hard to add these features using other tools such as ant, FitNesse, TestLink, svn, Chainsaw, etc.
Automation for continuous integration
- Start a test run, stop it, and evaluate results from an ant script
- Preload a CDS containing recordings and live streams
- Archive test results
Minimize the work to create test procedures
- Build new tests with a simple editing tool, such as a spreadsheet
- Provide simple looping constructs and control structures to minimize script coding
- Coordination of events between player and server is reliable and visible
- Tests may be organized into suites
- Test procedure events are parameterised (e.g. the number of seconds for a recording)
Capture information to analyze results, make it readily available, and automate the expected result
- Isolate certain dialogs between UPnP messages, like wireshark does
- Assertion mechanism, like JUnit or AutoXlet
Maintenance
- Adding major new functions and features to Rx does not murder existing test cases