Skip to end of metadata
Go to start of metadata

Defines the tests need to pass for a full Bitrepository system to be accepted.
Note that the tests found here tests a preconfigured system, and does not explore all the different configuration possibilities for a Bit repository system. Neither are all the interactions possible for individual component tested. Special finegrained tests are instead performed in the automatic component tests. 

Tests 

GetFile tests

Describes the tests needed to validate the GetFile functionality.

PutFile tests

Describes the tests needed to validate the PutFile functionality.

Delete tests

Describes the tests needed to validate the Delete functionality.

Replace tests

Describes the tests needed to validate the Replace functionality.

GetFileIDs tests

Describes the tests needed to validate the GetFileIDs functionality.

GetChecksums tests

Describes the tests needed to validate the GetChecksums functionality.

Integrity Service tests

Describes the tests needed to validate the Integrity Service functionality.

Alarm tests

Describes the tests needed to validate the Alarm functionality. This includes test of both the Alarm service and the alarm functionality on the contributing components.

Audit Trail tests

Describes the tests needed to validate the Audit Trail functionality. This includes test of both the Audit trail service and the audit trail service functionality on the contributing components.

Status tests

Describes the tests needed to validate the Status functionality. This includes test of both the Status service and the status functionality on the contributing components.

Robustness tests

Describes bad-case tests used to test the robustness of a Bitrepository system.

  • Checksum format testTests that the specified checksum formats are supported and that invalid formats are handled gracefully.
  • FileID format testExplorative test to investigate the systems robustness towards different fileID values.
  • Single point of failureTests that the varios mechanisms for avoiding single point of failures works correctly.
Sanity test

Test for checking the sanity of the system as a whole. This means a roundtrip with only sunshine usage of the system getting through all the core functionality

Load test

Investigates the limits of the system performance, by attempting to identify bottlenecks.

Security tests

Describes the tests needed to validate the Security functionality.

Quickstart test

Verifies the quickstart bundle.

Purpose

The tests are part of the suite of general tests which should be run in the following case:

  • Release test (Factory Acceptance Test (FAT)): Used to test release candidates in the integration before they are release officially.
  • Deployment test (Site Acceptance Test (SAT)): Used to verify that system works currently in the (production) environment.

The tests assume a fully deployed Bitrepository system is deployed with a single collection, at least 2 pillars and all reference services. The Webclient and command line client are used to perform the tests.

  • No labels