subsurface/tests/testgitstorage.h

#ifndef TESTGITSTORAGE_H
#define TESTGITSTORAGE_H

#include <QTest>

class TestGitStorage : public QObject
{
	Q_OBJECT
private slots:
	void initTestCase();
	void cleanup();

	void testGitStorageLocal_data();
	void testGitStorageLocal();
	void testGitStorageCloud();
	void testGitStorageCloudOfflineSync();
	void testGitStorageCloudMerge();
	void testGitStorageCloudMerge2();
	void testGitStorageCloudMerge3();
};

#endif // TESTGITSTORAGE_H
Add simple test for git storage This just makes sure that writing data to git storage and reading it back gives you the same result. Without the fixed generation of initial dive site UUIDs this fails. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 16:32:27 +00:00			`#ifndef TESTGITSTORAGE_H`
			`#define TESTGITSTORAGE_H`

			`#include <QTest>`

			`class TestGitStorage : public QObject`
			`{`
			`Q_OBJECT`
			`private slots:`
Use proper QTest initialization method in TestGitStorage Method originally called testSetup is more a precondition to test execution rather than an actual test. QTest recommends to use initTestCase for that purpose. Signed-off-by: Jeremie Guichard <djebrest@gmail.com> 2017-03-03 06:25:23 +00:00			`void initTestCase();`
Use QTest cleanup method for proper test shutdown In case of QCOMPARE failure, code following the comparison is not executed, this results in application state not being properly resorted and often gives several test failures, when only one test really fails. Using QTest cleanup method allows restoring proper state, before next test is executed. Signed-off-by: Jeremie Guichard <djebrest@gmail.com> 2017-03-03 06:33:25 +00:00			`void cleanup();`

Make TestGitStorage::testGitStorageLocal parametrizable Make use of QTest "Data Driven Testing", allowing to test multiple repo base path values. Signed-off-by: Jeremie Guichard <djebrest@gmail.com> 2017-02-24 07:02:32 +00:00			`void testGitStorageLocal_data();`
Add simple test for git storage This just makes sure that writing data to git storage and reading it back gives you the same result. Without the fixed generation of initial dive site UUIDs this fails. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 16:32:27 +00:00			`void testGitStorageLocal();`
Cloud storage: add test for simple save / load from our test account This will fail if the proxy settings of the user running the test are incorrect. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 19:15:45 +00:00			`void testGitStorageCloud();`
Cloud storage: test offline operation All this really does is make sure that the fast forward works if the local cache has received updates that haven't made it to the server, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 20:59:20 +00:00			`void testGitStorageCloudOfflineSync();`
Cloud storage: first test case for a very simple merge - We add a dive while offline. - On a different computer (here simulated by a different local cache) we add a different file. - Now we go back to the previous local cache (the one where we added a different dive in the first step) and take that online (i.e., connect to cloud storage). Now both of the new dives should have been added to our data file. This is a rather trivial test with no conflict and a straight forward merge. We need to add a lot more test cases to make sure this works as expected and doesn't leave the user with a corrupt state. Ideally whatever happens, the user should never see an error... Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 21:00:42 +00:00			`void testGitStorageCloudMerge();`
Cloud storage: second merge test, delete dive on one side, modify on other Delete a dive while offline, modify it from a different system while online. Then resync. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 23:23:21 +00:00			`void testGitStorageCloudMerge2();`
Add test case for multi line dive notes merging Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-30 20:00:32 +00:00			`void testGitStorageCloudMerge3();`
Add simple test for git storage This just makes sure that writing data to git storage and reading it back gives you the same result. Without the fixed generation of initial dive site UUIDs this fails. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> 2015-08-24 16:32:27 +00:00			`};`

			`#endif // TESTGITSTORAGE_H`