It should be possible to use SAI-Challenger as a 3rd party lib

[anton7811]

It should be possible to easily build a custom SAI-Challenger docker with additional software inside and custom test cases.

Currently, there are 2 main issues with this:

1. tests folder and working directory MUST be directly in /sai-challenger folder and only on the first level otherwise sai_npu load fails
2. SAI-Challenger packages are installed directly to the search path and make some mess there. I would expect to have them in the same location as it is done for PTF. When all modules are installed into ptf (specifically /usr/local/lib/python3.7/dist-packages/ptf) folder and any import can be done like from ptf import something.

Possible use case:
a. Custom SAI-Challenger client container for testing HW using customized tests and test tools
b. Using SAI-Challenger as a 3rd party module in other projects where folder structure may be different.

[andriy-kokhan]

Thank you for you input.
Just not sure I understood the first statement - "tests folder and working directory MUST be directly in /sai-challenger". Could you please provided an example of the expected usage?

[anton7811]

@andriy-kokhan, answering your question:
When I'm launching tests the working directory should be "/sai-challenger/". And If I have my own folder structure, e.g.: "/my/tests" or even "/sai-challenger/custom/tests" it won't work. So the user is obligated to have a specific folder structure. Putting custom user tests into the SAI-Challenger root may cause additional and unnecessary steps.

[andriy-kokhan]

This issue is expected to be addressed in scope of #26. Specifically, by 31fd92a