Forum Discussion

Florian_Hofmann's avatar
Florian_Hofmann
Contributor
10 years ago
Solved

Log analysis by groups rather than items

Hi everybody, maybe I'm lacking some imagination and just don't find the right words that might provide me with an answer from existing sources (or make for a more descriptive subject), sorry if ye...
  • Marsha_R's avatar
    Marsha_R
    10 years ago
    Hi Florian -



    We also have some tests that are repeated many times with different data, but we don't exclude them from the log because sometimes the data itself is a clue to finding the root cause of a test failure.  



    What we did do in our logs is start using the Group feature and the Append Log and Pop Log features inside all of our tests.  We use an Append/Pop for the beginning and end of each test, at the beginning and end of each Group, and at the beginning and end of any loops.  



    Take a look at my screenshot.  It looks like a lot of extra work in the code but each of those indents in the log is an Append and that really helps the readability when a test step fails.
Florian_Hofmann's avatar
Florian_Hofmann
Contributor
10 years ago
Starting to wonder if either my issue or the description thereoff might be a bit....far from other users' workflow.

If it's about the description, I'll try to give another version - let's assume I want to automate the following steps:



0) Start application, enter the GUI on first tab

1) enter Mastermode by pressing/clicking a key/button

2) perform some mastermode actions

3) leave Mastermode

4) switch to next tab

5) repeat steps 1-5 for all tabs of the GUI

 

Rather than creating one single item for testing of each tab, each of them including steps 1,3,4  It seemed natural to me to create one item for each step 1,3,4 respectively, one item for each possible step 2. 

The result ist that more than half of the items do test the same basic steps over and over again...is there a way to exclude them from being counted in the log analysis?

Or rather included into some bigger unit than items...



I have to admit, the question is more about aesthetics than about functionality, but I'm trying to produce some logs that at first glance tell also non-TC-users where problems might lie...