Missing unit tests approach for the Payload encoder

[Hoog-V]

Unit tests plan

The original library did not have unit tests our new library should have them (according to the class manual).

For me the following questions arise:

• What functionality are we going to test?
• Should we also test for compatibility with the original library?
• Are we going to deploy black-box and/or white-box testing (See slides WK3 IOT-LAB)?
• Should we test the payload decoder (Javascript thingy)
• What framework should we use for c++/c library (googletest, catch ?) might be useful to look at jetbrains c++ survey among c++ devs

I would highly appreciate it, if you help me elaborate on the questions besides answering :)

[Hoog-V]

As discussed, we start by testing the new cayennelpp, also to get familiar with the advantages and drawbacks of this new architecture. The first tests will test the setters functions which add certain variable types to the payload queue.

We are going to test the payload decoder when there is time left. We considered using other frameworks, but googletest is the most adopted and easiest to use.

The tests are mainly black box tests, though white box tests might be added in the future