| Excerpt |
|---|
Check that the repository can handle put and get of large number of files correctly (Not finished). |
| Info |
|---|
This tests requeres requires a dedicated system to be available, so no other tests can be run in the system during this test. |
The system should be started without audit trail service or integrity service running to avoid these service locking the system initially as the system comes under load.
The test should be start with a clean system.
...
- Start the integrity service
- Verify that the Audit trail Integrity service turns green in the webclient status overview.
- Tail the AuditTrailService IntegrityService log and verify that no errors are logged, and that the audit trail integrity service is able to retrieve the audit trails fileID and checksum list from the contributerspillars.
- Goto the AuditTrail overview in the webclient
- The webclient should display a list of audit trails, integrity overview should be able to load and should show a consistent collection without significant performance degradation.
- Run Manually run a couple of quiries integrity checks and verify that the view integrity is updated checked correctly without significant performance degradation.
...
- Start the audit trail service
- Verify that the Audit trail service turns green in the webclient status overview.
- Tail the AuditTrailService log and verify that no errors are logged, and that the audit trail service is able to retrieve the audit trails from the contributers.
- Goto the AuditTrail overview in the webclient
- The webclient should display a list of audit trails, without significant performance degradation.
- Run a couple of quiries and verify that the view is updated correctly without significant performance degradation.
File deletion
- Run the following command to delete the files:
Code Block Create script on first run.