Testing-Release.md

@@ -141,13 +141,24 @@ questionnaire phase
 - [ ] test execution of detection method of type `noCommands`, correctness of generated detection events (no incorrectly detected events, no missing occured events) 
 
 ## Testing Python backend
-- [ ] check if it is possible to create a sandbox (if the cloud project has enough resources to allocate number of sandboxes)
-- [ ] test all states of sandbox allocation unit (whether sandbox is in allocation or cleanup stage, fail or success)
+*When performing these tests, read ahead to see if maybe you can cover multiple test cases with the same sandbox to minimize allocations.*
+- [ ] check if it is possible to create a sandbox (if the cloud project has enough resources to allocate a number of sandboxes)
+- [ ] test all states of the sandbox allocation unit (whether the sandbox is in the allocation or cleanup stage, fail or success)
+  - [ ] test a simultaneous allocation of 4 sandboxes (using a simple sandbox [definition](https://gitlab.ics.muni.cz/muni-kypo-crp/prototypes-and-examples/sandbox-definitions/general-testing-definition)) at the same time (using a pool of 4 sandboxes and pressing the allocate all button). Test this about 10 times. There may be errors in the first stage due to the locking of Terraform workspace in the apply stage. This is expected but should not happen too often (If a failure of this type occurs, multiple sandboxes will often fail). Too often is more than twice out of the 10 allocations. ,A failure in networking stage may also occur, which should be rare and should be explored.
+    - [ ] if some sandboxes fail, try to re-run their allocation (do not delete them) and see if the re-run helped.
+    - [ ] when deleting sandboxes after these tests, try using different approaches of deletion. Try deleting one by one, the delete all, delete all failed and delete unlocked (lock sandboxes before)
+    - [ ] test that failed user ansible stage can be re-run, using a definition in which you create a new branch and deliberately add invalid information into the user ansible. A re-run will also fail, but test that is it possible.
+  - [ ] test allocating multiple sandboxes in a big pool (use the above definition and allocate a pool of 12 sandboxes) Repeat this three times.
+  - [ ] test that at any of the allocation stages, a cleanup can be performed, which should interrupt the allocation and start deallocating the sandbox (include a test case where you run the cleanup immediately after a sandbox has started allocating). Perform this test with pool of 4 sandboxes.
 - [ ] test APG (for example with this [definition](https://gitlab.ics.muni.cz/muni-kypo-crp/prototypes-and-examples/sandbox-definitions/network-attacks-apg))
-- [ ] test cleanup stage changes (mainly check that cleanup stage is not depending on the correct user git repo)
-- [ ] try to access a sandbox with ssh, spice and guacamole
-- [ ] check topology visualization
+- [ ] test that the cleanup stage is not depending on the correct user git repo
+- [ ] try to access a sandbox with ssh, spice, and guacamole
+  - [ ] test a big [sandbox definition](https://gitlab.ics.muni.cz/muni-kypo-crp/prototypes-and-examples/sandbox-definitions/five-os-sandbox), which includes different hosts of multiple different OSs, including windows and trz connecting to each one, also see if the ssh config is generated properly.
+- [ ] check the topology visualization is generated properly
 - [ ] `nmap` shouldn't discover hosts in private address ranges outside the topology definition. [Detailed description](https://gitlab.ics.muni.cz/muni-kypo-crp/kypo-crp-issues/-/issues/206).
+- [ ] test the docker containers in [this definition](https://gitlab.ics.muni.cz/muni-kypo-crp/prototypes-and-examples/sandbox-definitions/kypo-docker-containers), try to SSH into these docker containers
+- [ ] visit the resources agenda and try that the images can be correctly sorted using available methods, also test the only munikypo images filter
+- [ ] test the disk volumes [functionality in topology](https://gitlab.ics.muni.cz/muni-kypo-crp/kypo-crp-issues/-/issues/360) using [this branch](https://gitlab.ics.muni.cz/muni-kypo-crp/prototypes-and-examples/sandbox-definitions/five-os-sandbox/-/blob/testing-volumes/topology.yml#L9).
 
 ##### Testing [kypo-mitre-matrix-service](https://gitlab.ics.muni.cz/muni-kypo-crp/backend-python/kypo-mitre-technique-service)
 - [ ] try to run to service with all the other services and ensure that the map gets generated and can be viewed on the frontend