nestor-qa / nestor

Nestor
http://nestor-qa.github.io
MIT License
3 stars 0 forks source link

Add the Baseline/Version concept #49

Closed orenault closed 10 years ago

orenault commented 10 years ago

All Nestor object should have a Version number.

Thus, you may have the ability to manage versions and restore a TC/TS/TP after a change or do a Baseline.

The Baseline concept applies for a TP/an Execution: The Baseline is the version number of a TP/an Execution.

=> In the execution report, you can list all TS/TC with each version number, thus you can know exactly what have been tested. If TS/TC are modified after an execution, without baseline/version, you can be sure what has been done. => if you want to re-execute a TP (after a code fix), you should have to ability to execute a TP for a specific baseline. The execution will present the versions for all TS/TC used for the Baseline.

kinow commented 10 years ago

+1 we have discussed that in a previous meeting. It is not clear how to implement it though. The simplest way is either have a 'versions' table for each versioned table (what sounds not quite right) or find some different model. I'm working with the latter option... probably it's the longest path, but I think if we can find a good way to avoid duplicating tables, that may help us in the future with plug-ins too.

kinow commented 10 years ago

80% done. The database model has been updated, specification seems to be working fine. Next steps are:

Once these two are completed I'll merge, close the issue and will move to the next issue.

kinow commented 10 years ago

Planning done. Now the last remaining item is using test case versions in the executions too.

kinow commented 10 years ago

Closing now and moving to next issues. See last commit for implementation details and other notes.