[DTS/framework Bug 1438] Add additional packet checking functionality into DTS TestSuite

[bugzilla@dpdk.org]

[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]

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

            Bug ID: 1438
           Summary: Add additional packet checking functionality into DTS
                    TestSuite
           Product: DTS
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: framework
          Assignee: dts@dpdk.org
          Reporter: npratte@iol.unh.edu
  Target Milestone: ---

I think a discussion should be made around introducing extra functionality into
the TestSuite object within DTS. Old DTS, in numerous test suites, will
explicitly insert a payload into a frame; some test suites may even analyse the
contents within the frame to ensure that the specified payload was received
properly. A good example of this being the case in new DTS is the jumboframes
suite I am working on. Implementation of packet verification can be done in two
way: Assessing both layers two and three in all received packets to verify the
expected packet was received, or alternatively, dissecting and inspecting the
payload of each received packet and validating the user's previously defined
payload in within one of these received packets. For those that prefer the
latter, it might make sense to introduce a method that automatically does this
and introduce some kind of "default" payload in each packet if the user leaves
it unspecified. A potential benefit of this might be that we could create some
sort of "filter" method that, when called by the user, will return a list of
packets that contain a defined payload as a parameter, effectively getting rid
of all the the junk packets the test suite doesn't care about. In any case, I
think a good concern could be raised about why this sort of filtering is not
currently implemented in the framework currently.

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

[-- Attachment #2: Type: text/html, Size: 3866 bytes --]