Child pages
  • Large number of files test
Skip to end of metadata
Go to start of metadata

Check that the repository can handle put and get of large number of files correctly (Not finished). 

This tests requires a dedicated system, 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.

Basic operations

  1. Create a empty directory
  2. Run the following command in the new dir to create 100000 files:
    Create script on first run.
    
  3. Run the following command to put the 100000 files:
    Create script on first run.
    
  4. Run the following command to get the 100000 files:
    Create script on first run.
    
    1. Verify that the correct files are return

Webclient test

  1. Goto the status overview in the webclient, and verify that all component are running satisfactory, except the stopped integrity and audit trail service.
  2. Goto the alarm overview in the webclient.
    1. An empty list of alarms is show.
  3. Try to get a list of all the fileIDs through the webclient.
    1. The webclient should display a list of fileIDs, without significant performance degradation.
  4. Try to get a list of all the checksums through the webclient.
    1. The webclient should display a list of checksums, without significant performance degradation.

Integrity service test

  1. Start the integrity service
    1. Verify that the Integrity service turns green in the webclient status overview.
    2. Tail the IntegrityService log and verify that no errors are logged, and that the integrity service is able to retrieve the fileID and checksum list from the pillars.
  2. Goto the AuditTrail overview in the webclient
    1. The webclient integrity overview should be able to load and should show a consistent collection without significant performance degradation.
    2. Manually run a couple of integrity checks and verify that integrity is checked correctly without significant performance degradation.

Audit trail service test

  1. Start the audit trail service
    1. Verify that the Audit trail service turns green in the webclient status overview.
    2. 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.
  2. Goto the AuditTrail overview in the webclient
    1. The webclient should display a list of audit trails, without significant performance degradation.
    2. Run a couple of quiries and verify that the view is updated correctly without significant performance degradation.

File deletion

  1. Run the following command to delete the files:
    Create script on first run.
    
  • No labels