Structure timestamps

[silasmahler]

Hey @florianluediger, heres the present state 👍

What works now/has been done:

• Generation of database-entries for (Spring)ApplicationContextEvents + storing and reading from in-memory-db
• Generation of timemeasurements for testcontext (classes, methods) - TestBenchmarkclass
• Annotate Testclass with @junitinsights if you want to use the features to measure the testclass and all its methods
• Annotate Testmethods with @nojunitinsights if you dont want to measure a certain method

What was done why:

• Measuring of ApplicationContexts was decoupled from measuring of Testcontexts cause it caused a ton of problems with the junit5 architecture
• in junit extension no standard dependency injection is usable (Hence no @repository and @service -construct), so the context-store is used which problematically disappears after testexecution so the data needs to be saved properly

What has to be done:

• Enable @junitinsights to also catch the applicationevents (Could be difficult); maybe multiple more annotations needed
• Save data for testcontexts
• Put together all data in a similar fashion
• Generate fancy html report; see Visualization base #14
• Differentiate between time spent on Spring related actions and the rest; see Differentiate between time spent on Spring related actions and the rest #15

[silasmahler]

Fürs mergen können die Inhalte dieser branch genutzt werden

[florianluediger]

This seems to work fine so far, however before merging we also need to add the timestamps from the JUnit extension to the dataset and export the data in a csv file or something similar.

[silasmahler]

This seems to work fine so far, however before merging we also need to add the timestamps from the JUnit extension to the dataset and export the data in a csv file or something similar.

Seems like a good option

[florianluediger]

After taking a step back, I realized that it is probably much easier to write the data directly into a csv file without the detour over the database. This also was really simple to implement and streamlined the code a fair bit. This is now ready for review and we can focus on the creation of the visual report from now.

Closes #4