Could anyone give me some hints about best practice about tests grouping and ordering?
I'm thinking about hierarchies of tests, or something like that.
For example, I have class A and class B.
The suite for class A - TestA - tests base set of features, ie. stating, opening and closing a file.
Next, the suite for class B - TestB - tests set of specific features, ie. formating, writing, reading, parsing data to/from a file.
Ideally, I'd like to not to run tests from the TestB if tests from the TestA fail.
Is anything like this supported by CppUnit ?
--
Mateusz Loskot
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, you can for example create a CppUnit::TestSuite for your A Tests, and onether TestSuite For B Tests
and with a booléan for example if(testSuccess) run the B TestSuite else u don't run the tests.
I hope this will help u.
Otmane.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Could anyone give me some hints about best practice about tests grouping and ordering?
I'm thinking about hierarchies of tests, or something like that.
For example, I have class A and class B.
The suite for class A - TestA - tests base set of features, ie. stating, opening and closing a file.
Next, the suite for class B - TestB - tests set of specific features, ie. formating, writing, reading, parsing data to/from a file.
Ideally, I'd like to not to run tests from the TestB if tests from the TestA fail.
Is anything like this supported by CppUnit ?
--
Mateusz Loskot
Hi, you can for example create a CppUnit::TestSuite for your A Tests, and onether TestSuite For B Tests
and with a booléan for example if(testSuccess) run the B TestSuite else u don't run the tests.
I hope this will help u.
Otmane.