Reduce initial load

[conradstrassburger]

Changes

Rewrites the data model so that individual logMessages aren't referenced directly by their containing objects (ExecutionContext and TestStepActionEntry), and instead by id from a different file that only contains logMessages. Corresponding generation and display logic is adapted.

Motivation

Upon initial load, opening the Testerra Report can take quite some time. An approach to reduce load times by splitting data from the execution file into multiple files was explored. LogMessages make up the bulk of the file size of the execution file (~80%). The Dashboard is the first page loaded when entering the report. Its startup is slowed down by having to load all LogMessages within the execution file, even though only a handful of them are needed at this point. The LogMessages are loaded as a different file in the background, and we can display the dashboard more quickly.

Type of change

• [x] New feature (non-breaking change which adds functionality)

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing tests pass locally with my changes

Review

Commits are structured logically to allow indiviual review.

[martingrossmann]

@conradstrassburger There is a heavy load in the Logs or Tests view in case of bigger log files. You can see that in browser dev tools.

[martingrossmann]

This change will merge into a new branch to fix merge conficts of Testerra 2.8