Add tests for user creation/deletion/retrieval

Summary

Tests for caosdb-cpplib!40 (merged)

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

test/test_user.cpp

@@ -18,10 +18,10 @@
  * along with this program. If not, see <https://www.gnu.org/licenses/>.
  *
  */
-#include "caosdb/acm/user.h"             // for User
-#include "caosdb/connection.h"           // for Connection, VersionInfo, path
-#include "caosdb/exceptions.h"           // for TransactionError
-#include "caosdb_test_utility.h"         // for EXPECT_THROW_MESSAGE
+#include "caosdb/acm/user.h"       // for User
+#include "caosdb/connection.h"     // for Connection, VersionInfo, path
+#include "caosdb/exceptions.h"     // for TransactionError
+#include "caosdb_test_utility.h"   // for EXPECT_THROW_MESSAGE
 #include <gtest/gtest-message.h>   // for Message
 #include <gtest/gtest-test-part.h> // for SuiteApiResolver, TestPartR...
 #include <gtest/gtest_pred_impl.h> // for Test, TestInfo, TEST, EXPEC...
@@ -60,7 +60,10 @@ TEST(test_user, test_create_single_user_success) {
   auto re = connection->RetrieveSingleUser("CaosDB", "user1");
   EXPECT_EQ(re.GetName(), user.GetName());
   connection->DeleteSingleUser("CaosDB", "user1");
-  EXPECT_THROW_MESSAGE(connection->RetrieveSingleUser("CaosDB", "user1"), caosdb::exceptions::Exception, "The attempt to execute this transaction was not successful because an error occured in the transport or RPC protocol layer. Original error: 5 - This account does not exist.");
+  EXPECT_THROW_MESSAGE(
+    connection->RetrieveSingleUser("CaosDB", "user1"), caosdb::exceptions::Exception,
+    "The attempt to execute this transaction was not successful because an error occured in the "
+    "transport or RPC protocol layer. Original error: 5 - This account does not exist.");
 }
 
 } // namespace caosdb::connection