unit_tests
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
unit_tests [2016/09/08 11:49] – mhatz | unit_tests [2016/09/09 07:38] – mhatz | ||
---|---|---|---|
Line 5: | Line 5: | ||
For Mail2Voice Next, we introduced unit tests. Units tests are useful to ensure that every classes/ | For Mail2Voice Next, we introduced unit tests. Units tests are useful to ensure that every classes/ | ||
- | The unit tests written for Mail2Voice are base on QTest suite. | + | The unit tests written for Mail2Voice are based on QTest suite. |
- | ===== HOWTO : writing a unit test for a class ===== | + | ===== HOWTO writing a unit test for a class ===== |
- | Each class of Mail2Voice must have its dedicated unit tests to check every method | + | Each class of Mail2Voice must have its dedicated unit tests to check every methods |
==== Example ==== | ==== Example ==== | ||
Line 34: | Line 34: | ||
</ | </ | ||
- | MyClass is a very simple class that does two things : incrementing an internal variable and setting an internal text. Nothing special | + | MyClass is a very simple class that does two things : incrementing an internal variable and setting an internal text. Nothing special |
- | Wait, mistakes are common and even if you are sure of your code, are you sure that no one else won't introduce errors in your code? That, is where unit tests are useful : ensuring your code is correct and will stay correct over time. Saving you a lot of time of debugging in the future. | + | Wait, mistakes are common and even if you are sure of your code, are you sure that no one else won't introduce errors in your code? That, is where unit tests are useful: ensuring your code is correct and will stay correct over time. Saving you a lot of time of debugging in the future. |
==== What to test? ==== | ==== What to test? ==== | ||
Line 42: | Line 42: | ||
So, what do we have to test exactly? | So, what do we have to test exactly? | ||
- | * Basically every methods: | + | Basically every methods: |
* first, the constructor because it is in charge of initializing an object of type MyClass, | * first, the constructor because it is in charge of initializing an object of type MyClass, | ||
* the count() and text() methods to make sure they return correct values, | * the count() and text() methods to make sure they return correct values, | ||
Line 49: | Line 49: | ||
To write a unit test, you have to ask yourself what behavior is expected for each method. Let's do this exercise: | To write a unit test, you have to ask yourself what behavior is expected for each method. Let's do this exercise: | ||
- | * MyClass(): the constructor must initialize the object, so it must initialize the members m_count and m_text. But, to which values? This have to be specified somewhere otherwise the objects could be inconsistent. | + | |
- | ** For our example, we will pretend that m_count must be initialize | + | * For our example, we will pretend that m_count must be initialized |
- | * increment(): | + | |
- | ** For our example, we choose the second option: never go to negative value. | + | * For our example, we choose the second option: never go to negative value. |
- | * setText(const QString& | + | |
- | * count() and text() methods must always return the current value. | + | |
==== Coding the unit tests ==== | ==== Coding the unit tests ==== | ||
Line 67: | Line 67: | ||
<code cpp> | <code cpp> | ||
#include " | #include " | ||
+ | #include " | ||
#include < | #include < | ||
- | class TestMyClass : public QObject | + | class TestMyClass : public QObject, public PropsTester< |
{ | { | ||
Q_OBJECT // Because we derive from QObject and want Qt features | Q_OBJECT // Because we derive from QObject and want Qt features | ||
Line 87: | Line 88: | ||
</ | </ | ||
+ | The PropsTester class is a convenience to check properties against their default values. While it is not mandatory, it is highly recommended to ease the test of class members integrity. | ||
+ | The implementation of TestMyClass will look like this: | ||
+ | <code cpp> | ||
+ | #include < | ||
+ | #include " | ||
+ | TestMyClass:: | ||
+ | { | ||
+ | // m_propsCheckList stores lambdas functions that check the default value of class members. | ||
+ | // Each lambda function is associated with a name (" | ||
+ | m_propsChecklist.append({" | ||
+ | m_propsChecklist.append({" | ||
+ | } | ||
+ | |||
+ | void TestMyClass:: | ||
+ | { | ||
+ | MyClass myClass; // We just create a myClass object... | ||
+ | checkDefaultProperties(myClass, | ||
+ | // Note that the second parameter is a list of members to NOT check. | ||
+ | } | ||
+ | |||
+ | |||
+ | void TestMyClass:: | ||
+ | { | ||
+ | MyClass myClass; | ||
+ | | ||
+ | for(int i = 1; i <= 10; ++i) | ||
+ | { | ||
+ | myClass.increment(); | ||
+ | QVERIFY2(myClass.count() == i, "Count is incorrect." | ||
+ | checkDefaultProperties(myClass, | ||
+ | } | ||
+ | } | ||
+ | |||
+ | void TestMyClass:: | ||
+ | { | ||
+ | MyClass myClass; | ||
+ | | ||
+ | for(int i = 0; i < 2147483647; ++i) | ||
+ | { | ||
+ | myClass.increment(); | ||
+ | } | ||
+ | | ||
+ | QVERIFY2(myClass.count() == 2147483647, "Count is incorrect." | ||
+ | | ||
+ | myClass.increment(); | ||
+ | QVERIFY2(myClass.count() == 2147483647, "Count is incorrect." | ||
+ | | ||
+ | checkDefaultProperties(myClass, | ||
+ | } | ||
+ | |||
+ | void TestMyClass:: | ||
+ | { | ||
+ | MyClass myClass; | ||
+ | myClass.setText(" | ||
+ | QVERIFY2(myClass.text() == "Hello world!", | ||
+ | checkDefaultProperties(myClass, | ||
+ | } | ||
+ | |||
+ | void TestMyClass:: | ||
+ | { | ||
+ | MyClass myClass; | ||
+ | myClass.setText("" | ||
+ | QVERIFY2(myClass.text() == " | ||
+ | checkDefaultProperties(myClass, | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | |||
+ | Then, in the main.cpp file of the unittests subproject, you have to instantiate a TestMyClass object and add it to the list of tests to run: | ||
+ | |||
+ | <code cpp> | ||
+ | int main( int argc, char *argv[]) | ||
+ | { | ||
+ | int ret = 0; | ||
+ | |||
+ | TestContact tstContact; | ||
+ | TestEmail tstEmail; | ||
+ | TestAccount tstAccount; | ||
+ | TestAttachment tstAttachment; | ||
+ | TestServerSettings tstServerSettings; | ||
+ | TestMyClass tstMyClass; // <-- instantiation | ||
+ | |||
+ | ret = executeTests(argc, | ||
+ | {& | ||
+ | & | ||
+ | & | ||
+ | & | ||
+ | & | ||
+ | & | ||
+ | |||
+ | return ret; | ||
+ | } | ||
+ | </ | ||
+ | ==== Running unit tests ==== | ||
+ | Well, that is the simplest part, just select the unittests subproject in QtCreator, compile it and run it! |
unit_tests.txt · Last modified: 2023/04/25 16:52 by 127.0.0.1