| ... | ... | @@ -142,7 +142,7 @@ questionnaire phase |
|
|
|
|
|
|
|
## Testing Python backend
|
|
|
|
*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)
|
|
|
|
- [ ] check if it is possible to create a sandbox (if the cloud project has enough resources to allocate a number of sandboxes, try creating a pool which has too many sandboxes and try to allocate them. It should not be possible.)
|
|
|
|
- [ ] 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.
|
| ... | ... | |