Databases
StackOverflow2013
Postsdbo
POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
    primarykey
    data
    text
    <p>I have written C++ tests with GTest which basically work like this</p> <pre><code>MyData data1 = runTest(inputData); MyData data2 = loadRegressionData(); compareMyData(data1,data2); </code></pre> <p>with</p> <pre><code>void compareMyData(MyData const&amp; data1, MyData const&amp; data2) { ASSERT_EQ(data1.count, data2.count); //pseudo: foreach element in data1/data2: EXPECT_EQ(data1.items[i], data2.items[i]); } </code></pre> <p>Now I would like to save the <code>data1</code> contents to a file IFF the test fails and I don't see an elegant solution yet.</p> <hr> <p>First approach: <strong>Make <code>compareMyData</code> return the comparison result.</strong> This can't work with the <code>ASSERT_EQ</code> which is fatal. Writing <code>if (!EXPECT_EQ(...))</code> doesn't compile so the only way I found is </p> <pre><code>bool compareMyData(MyData const&amp; data1, MyData const&amp; data2) { EXPECT_EQ(data1.count, data2.count); if (data1.count != data2.count) return false; //pseudo: foreach element in data1/data2: { EXPECT_EQ(data1.items[i], data2.items[i]); if (data1.items[i]!= data2.items[i]) return false; } } </code></pre> <p>Not very elegant :-(</p> <hr> <p>Second idea: <strong>Run code when the test failed</strong></p> <p>I know I can implement <code>::testing::EmptyTestEventListener</code> and get notified if a test fails, but that doesn't give me the data I want to write to file and it is "far away" from the place I'd like it to have. So my question here is: Is there a way to run code at the end of a test if it failed (e.g. catching an exception?).</p> <hr> <p>To ask more general: how would you solve this?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPhilipp
    1. USPhilipp
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy do you want the data in a file?
      singulars
      1. POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
      1. USdoctorlove
    2. CO@doctorlove: the tested code performs numeric calculations on large input data sets. By writing the results to disk I can load and analyze them properly with visualization tools to see what went wrong and when. (These are regression tests that also test some integration of the whole system. We have Unit tests as well where evaluation of the test data is simpler.) If everything's fine, I don't want to write the data to file because the amount of data is big.
      singulars
      1. POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
      1. USPhilipp
    3. COGoogle Test has a number of ways to deal with this. Check out their wiki section on detecting failures inside the test and in subroutines in particular the documentation on [Propagating Fatal Failures](https://github.com/google/googletest/blob/master/googletest/docs/advanced.md#propagating-fatal-failures).
      singulars
      1. POChecking result of EXPECT_* macros in GTest or run code when ASSERT_* failed
      1. USVladLosev
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload