[Bug 965] Create DTS test dev document

[bugzilla@dpdk.org]

https://bugs.dpdk.org/show_bug.cgi?id=965

            Bug ID: 965
           Summary: Create DTS test dev document
           Product: DTS
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: framework
          Assignee: dts@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
  Target Milestone: ---

The audience for this document are the engineers who are writing the test
cases.

1) Document a process to start writing a test case. It can start with copying a
template from the repo. Add some simple test case examples. Output examples for
testpmd functions could be helpful.

2) Highlight the existence of configuration clean up functions that need to be
called after every test case and test suite. Python meta classes feature can be
used here to enforce the use of cleanup functions. The base class would be
replaced with a meta class. The existing test cases might need to be changed to
conform to this meta class (it might mean adding nops to several functionality
the meta class requires).

3) Make it clear that the test cases have to be based off of testpmd. If
testpmd is lacking features, they need to be added/requested.

4) Document coding and contributor guidelines.

5) Document the allowed cases for using “eval” within the code, which should be
avoided, along with reflection and type modification.

6) Document how to handle breaking changes (i.e. changes to configuration files
or json output or other interfaces intended for machine interactions [don’t
break the robots]).

7) Capture the procedure to move to latest versions of the dependencies

-- 
You are receiving this mail because:
You are the assignee for the bug.