IDE-300 number of virtual layers changed from 2 to 3

[dorastr]

https://catrobat.atlassian.net/browse/IDE-300

• [x ] Include the name of the Jira ticket in the PR’s title
• [ x] Include a summary of the changes plus the relevant context
• [ x] Choose the proper base branch (develop)
• [ x] Confirm that the changes follow the project’s coding guidelines
• [ x] Verify that the changes generate no compiler or linter warnings
• [ x] Perform a self-review of the changes
• [x ] Verify to commit no other files than the intentionally changed ones
• [x ] Include reasonable and readable tests verifying the added or changed behavior
• [x ] Confirm that new and existing unit tests pass locally
• [x ] Check that the commits’ message style matches the project’s guideline
• [x ] Stick to the project’s gitflow workflow
• [x ] Verify that your changes do not have any conflicts with the base branch
• [x ] After the PR, verify that all CI checks have passed
• [ x] Post a message in the catroid-stage or catroid-ide Slack channel and ask for a code reviewer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dorianpercic]

Change looks good, there are failing Unit Test cases though, which would need to get adjusted: Jenkins Job

You can execute locally the testCatroidDebugUnitTest Gradle Job to execute the Unit Tests and fix them. As far as I checked only the testBoundaryBackground seems to fail. Maybe it would be good to also double check the other failing Instrumented Unit Test cases, if they are because of this constant change.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud