[dpdk-dev] [PATCH v2 01/11] app/test: introduce resources for tests

2016-05-12 Thread Jan Viktorin
On Thu, 12 May 2016 17:19:21 +0200 Thomas Monjalon wrote: > 2016-05-10 20:13, Jan Viktorin: > > +REGISTER_TEST_COMMAND(resource_cmd); > > Should you add this test in group 1 of autotest_data.py? Will do for v3. This way: ... 84

[dpdk-dev] [PATCH v2 01/11] app/test: introduce resources for tests

2016-05-12 Thread Thomas Monjalon
2016-05-10 20:13, Jan Viktorin: > +REGISTER_TEST_COMMAND(resource_cmd); Should you add this test in group 1 of autotest_data.py?

[dpdk-dev] [PATCH v2 01/11] app/test: introduce resources for tests

2016-05-12 Thread Thomas Monjalon
2016-05-10 20:13, Jan Viktorin: > +struct resource { > + const char *name; /** Unique name of the resource */ > + const char *begin; /** Start of resource data */ > + const char *end; /** End of resource data */ > + TAILQ_ENTRY(resource) next; > +}; There is no doxygen generated

[dpdk-dev] [PATCH v2 01/11] app/test: introduce resources for tests

2016-05-10 Thread Jan Viktorin
Certain internal mechanisms of DPDK access different file system structures (e.g. /sys/bus/pci/devices). It is difficult to test those cases automatically by a unit test when such path is not hard-coded and there is no simple way how to distribute fake ones with the current testing environment. Th