Try to add missing tests for real-time visual editing tools and, if possible, automate the running on them.

[tracygardner]

[Zishan-Rahman]

As discussed privately.

[julianharty]

@Zishan-Rahman @tracygardner I'm happy to assist with this. If so, some more details of what the tests would be expected to check|test would be helpful as would some examples you'd like the tests to exercise. Pointers to existing tests for the real-time visual editing tools may also help by providing patterns of the type of tests you'd like.

[Zishan-Rahman]

@Zishan-Rahman @tracygardner I'm happy to assist with this. If so, some more details of what the tests would be expected to check|test would be helpful as would some examples you'd like the tests to exercise. Pointers to existing tests for the real-time visual editing tools may also help by providing patterns of the type of tests you'd like.

@julianharty (sorry for the late reply and for the ping) I'm more than happy for you and James (@workroomprds) to assist with this. I was meant to have got to writing tests for the visual tools issues and fixes I worked on during August and September (I'm now working on FlockXR's UI themes and other FlockXR things this month).

As I believe he told you already, James and I had a chat a few weeks back about what I want to write tests for if and/or when I have the chance. Firstly, I'd like to test the things I worked on related to the visual tools, such as pressing F to zoom into a specific mesh, making sure multi-meshes/composite meshes show their whole bounding boxes when selected and creating a sky colour block with the colour picker. I implemented the features themselves but never got around to writing tests for them, which I've been meaning to do while also being very busy. Also, the current Playwright tests test for FlockXR's boot up, presence of basic UI elements and ability to open one of the toolbox categories, but nothing else beyond that, and we're especially aiming to automate the testing much of the UI and end user functionality that will come into use with FlockXR, such as the adding of meshes and changing of the sky colour on the canvas with the gizmos, as well as the adding of code to the editor and the live updates of certain types of code block (for which Tracy and I have worked on implementing). Tracy has also been working really hard on making sure events such as mesh block creation get undone properly, and there are still issues that need to be fixed (in fact, one of my pull requests had to be reverted by Tracy because the undoing of certain events got botched with it), so it would be nice to test for that as well. I haven't had a look at the Chai and Mocha tests in a while, so I'll have to have a look there and reply back to you and James on that. I am aware that there are some ongoing code coverage issues with those tests that James was trying to work on.