Description of problem: Right now retrace-server has no tests which are checked into the repository and can be run prior to deployment. Testing is quite critical since the project is written in python and often bugs are not found until run-time. This RFE requests some initial tests to be written which can be run in an automated fashion before deployment. Areas covered should include: 1. all command line interfaces and common options. 2. testing of the web interface and deployment of both 3. sample vmcores from all major releases, and for all special scenarios (i.e. ones where makedumpfile is run, ones where makedumpfile is skipped, compressed with various compression techniques, etc). We may not need to check these in, we just need a way to specify a series of vmcores for the tests we define. * NOTE: we have sample vmcores internally We can start with a test plan and a few small but important tests which give a pass / fail. Then over time we should add to the tests. Right now we just have a series of vmcores which we run for various releases to ensure nothing is broken, as well as some automated analysis which runs post retrace-server. Version-Release number of selected component (if applicable): 1.12 or 1.13 Actual results: No regression tests exists. Expected results: Some regression tests exists. Additional info:
Related bugs with specific code that should have separate test cases: https://bugzilla.redhat.com/show_bug.cgi?id=1396629 https://bugzilla.redhat.com/show_bug.cgi?id=1396623 https://bugzilla.redhat.com/show_bug.cgi?id=1396628
There were effort to make retrace server testable. Now it is possible to run 'make check'. You have to execute it as root, since it uses mock. Some work was also done to solve this, but it is not ready yet. But after solving the root issue, it should be fairly easy to add different tests. Then it would be probably the best to write unit tests.
Some work has been done. Closing this WONTFIX. But this has been open for years, and it's unclear upstream project status going forward.