Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From looking at the source code of gtest the only case if there are no parametrized tests available is on Windows using VC7.1 with disabled exceptions:</p> <pre><code>// We don't support MSVC 7.1 with exceptions disabled now. Therefore // all the compilers we care about are adequate for supporting // value-parameterized tests. #define GTEST_HAS_PARAM_TEST 1 </code></pre> <p>So, you'll need to check how your MinGW was built and probably update it? And can you run the gtest unit tests to see if they execute the typed parameters test?</p> <p>More information on MinGW:</p> <p>On their <a href="https://code.google.com/p/googletest/wiki/FAQ#Can_I_use_Google_Test_on_MinGW?" rel="nofollow">FAQ</a> they report that when using MinGW the following compile option for building gtest is required: <code>PATH/TO/configure CC="gcc -mno-cygwin" CXX="g++ -mno-cygwin"</code>.</p> <p>Complete Example:</p> <pre><code>#include &lt;gtest/gtest.h&gt; namespace EnsembleClustering { class ParametrizedGTest: public testing::TestWithParam&lt;int&gt; { public: ParametrizedGTest(); virtual ~ParametrizedGTest(); }; ParametrizedGTest::ParametrizedGTest() { } ParametrizedGTest::~ParametrizedGTest() { } TEST_P(ParametrizedGTest, testParameter) { int n = GetParam(); EXPECT_EQ(n, GetParam()); } INSTANTIATE_TEST_CASE_P(ParametrizedGTestInstance, ParametrizedGTest, ::testing::Values(100)); } /* namespace EnsembleClustering */ int main(int argc, char* argv[]) { ::testing::InitGoogleTest(&amp;argc, argv); return RUN_ALL_TESTS(); } </code></pre> <p>I compiled this code using the following compiler call on Mac OS X 10.8:</p> <pre><code>g++ -IGTEST_INCLUDE_DIR -LGTEST_LIB_DIR -lgtest -o tt2 tt2.cpp </code></pre> <p>Where <code>GTEST_INCLUDE_DIR</code> and <code>GTEST_LIB_DIR</code> are the path where header and library files are stored. When you compile and execute, what happens?</p>
    singulars
    1. This table or related slice is empty.
    1. POGoogletest Parametrized tests crash
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgrundprinzip
    1. USgrundprinzip
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGoogletest Parametrized tests crash
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COI'm on Mac OS X 10.8. I should have added that to the question before.
      singulars
      1. PO
      1. USclstaudt
    2. COWhen I build this as a standalone project with these options: https://gist.github.com/4626770 - it works fine.
      singulars
      1. PO
      1. USclstaudt
    3. COWell, it also works now in my original project! I haven't touched the code of the test, but I've changed the compiler settings. In particular, I removed the flag `-D_GLIBCXX_DEBUG`, which was the cause of another extremely strange crash. The bounty is still yours, since you really looked into the issue.
      singulars
      1. PO
      1. USclstaudt
 

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