Forum Discussion

primoz_pirc's avatar
primoz_pirc
New Contributor
11 years ago

Analyzing big test results log file

We have about about 500 test items in one project file.

Each day after automated tests are finished we have to go through Errors and Warnings.

If there is only 5 test that needs to be checked I have to scroll up and down to find these filed tests. 



Using Goto next error or next warning is not good enough. Even if used only "Test Log" item is changed. I need the test item name in "Log Items" to get focus.



Is there a way to only show Test Items with Errors and Warnings. I only need to check those tests not the ones that are passing. Simple filter would be good enough.



Maybe a solution already exists so I would be really happy to hear it.

This is a repeatable daily task that really takes too much time. It could be done so much faster and easyier.



Thanks for help

Best regards

PP

5 Replies

  • chrisb's avatar
    chrisb
    Regular Contributor




    1. Build your test run in the 'Test Items' window of project.

    2. Run the tests.

    3. Double click on the test run displayed in the project logs.

    4. In the project log window click on the root of the project tree. 

    5. Select filter options by clicking checkboxes.

    6. Browse the filter results. To view the contents of the test double click on the test name.



    Take a look at the attached screenshot. You can see a test run consisting of 10 tests. A filter is applied to only show the tests that have errors.



    Another more advanced option would be to write a script to do email notifications. I prefer this method. I receive a list of failed tests in an email and much prefer this to browsing the .mht file.
  • At the top of the test log there are checkboxes to filter what is shown, untick everything except Error and Warning. 
  • This only filters out errors and warnings for the currently selected test item.

    This is not the solution.

    In my attachment you can see many test items, most of them are passing but I would like to see only the ones with Errors and warnings....



    Any idea about how this could be solved ?
  • Yes, I also use this from time to time. But once you hit the bottom level test there is no easy way to get back. You have to scroll up and search to find the parrent level of test.



    This is still not fast enough.



    I would like to have that filter on the left side in "Log Items"...



    As i am testing this workflow again this way might not be that bad.

    But with use of arrow button "Move focus to parrent level"



    Still a filter on the left side would be nice :)



    If there is anybody that knows of a faster workflow let us know.

    thanks

  • I am considering adding an event handler for log message to write out test results to a .CSV file.  The scheme I am considering using is to create a custom Priority value as a global variable and use it as a parameter when logging a message, and having the event handler trap messages with that priority.  The trapped messages would be written to a .CSV file.  I would only need to check the .CSV file to see the results of the test cases.  The .CSV file could be imported into a master QA database.



    To me the TC Log is more like a log4j type of log that records script execution results.  But it also mixes test case results with the runtime results.  That is the problem we are both trying to solve. 



    Let us know what you come up with.  I am very interested in this topic.



    TIA