User:Vineetnadella/sandbox

Test Development Flow
1) When planning a hill please make sure, each Test Case should have a test JIRA and each test JIRA results in a SPEC JIRA, i.e 1:1 mapping.

2) When you are creating a test spec please update the Test Category (swimlane the test belongs to), SSD_Feature (feature test maps to in testplan). Description: Test  (name of test your test file).

SSD Feature: links to a Feature in TestPlan and should also be a folder inside the swimlane where the test will live. Eg. trunktests\ctftests\Media\Optane\feature

Type of Test: Internally Developed – FFT (System) \ Internally Developed – Module (harness).

Please make sure the above fields are accurate as they can affect the testplan.

3) If you are developing a CTF system test, please make sure that each testSpec i.e. each testCase should have its own .py file.

4) If you are developing a ModuleTest test, please make sure the full test name ends in "Test".

eg. XU_DECLARE_FIXTURE("FastCtxPingPongBasicTest", setup, pingPongTest, teardown)• eg. XU_DECLARE_FIXTURE(cpuCtxSaveRestoreTest)•

5) After you are done writing a test, the path for the template should be exactly the same as where the test lives, i.e. trunktests\templates\Media\Optane\xxx\.tpl

6) The name of the template should be TestCaseName_SPEC-3456.tpl. If there is a need to re-Use a template to feed different arguments to a test, then we use a UniqueIdentifier and the template is named as TestCaseName_UI_SPEC-3456.tpl. Eg. Using same test to run Diff kind of workloads.

7) The reportName inside a tpl should be ReportName = Feature_test1_SPEC-3456,if tpl name has a UI ReportName = Feature_test1_UI*_SPEC-3456.