On 07/25/2012 10:37 AM, Martin Mrazik wrote: > Hi, > > I'm not sure everybody knows it but we are using a 3rd party company for > some manual testing. It is quite common (and useful) to use test-case > management systems instead of text files, spreadsheets and similar. That > means we need to import tests from manual-tests/ into such system(s). > > It is therefore _important_ to follow a certain structure for all manual > test-cases so we can automate the process. > > I would like to ask everybody to do the following: > 1. when writing a new test-case follow the TEST_TEMPLATE.txt. All > sections are mandatory. If you don't want to add anything into a section > leave an empty line. Name the sections as in the template (e.g. > "Expected Result" is correct; "Outcome" is wrong) > > 2. when doing a code-review, please check the manual-tests for > compliance with TEST_TEMPLATE.txt > > If you do this you will save us some time and make it easier to test > unity in non-Canonical environments. >
Perhaps it'd make sense to add a simple (python-based?) parser which would check the format during `make check`? That way the mergers would make sure that the test cases are correct and we won't have to correct them every now and then. Michal -- Mailing list: https://launchpad.net/~unity-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~unity-dev More help : https://help.launchpad.net/ListHelp
