-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Affects Version/s: record ingestion (benchmark)
-
Fix Version/s: record ingestion (benchmark)
-
Component/s: None
-
Labels:
-
Epic Link:
-
Sprint:Flamebird 7 - Parallax, Flamebird 8 - Two-face, Flamebird 9 - The Leader
-
Story Points:5
Objectives
Extend IG API benchmark driver to allow the in-place record declaration strategy to be configured for a test run.
Configuration Options
- In-place Record Declaration - indicates whether this test run should be uploading content and declaring it as records
- Site Id - the collaboration site from which the records will be declared. Mandatory.
- Folder Path(s) - relative paths within document library from which documents will be declared as records. Multiple paths can be provided. If no folder provided then records declared anywhere in the site document library.
- Record Declaration Limit - the maximum number of documents to declare, if 0 all records found are declared.
Note
- This assumes that documents have already been loaded into the relevant site document library.
- Ideally as records are declared within a site they should be selected randomly from within the specified folder hierarchy.
Acceptance Criteria
Given that I have created a test execution
And configured in-place record declaration off
When the benchmark driver is executed
Then no in-place record declaration occurs
Given that I have created a test execution
And configured in-place record declaration on
When the benchmark driver is executed
Then in-place record declaration occurs
Given that I have created a test execution
And configured in-place record declaration on
And configured the site id
And not configured a folder path
When the benchmark driver is executed
Then documents are declared from anywhere within the document library of the site
And all documents found are declared as records
Given that I have created a test execution
And configured in-place record declaration on
And configured the site id
And configured one or more folder paths
When the benchmark driver is executed
Then documents are declared from anywhere within the specified folders and any of their sub-folders
And all documents found are declared as records
Given that I have created a test execution
And configured in-place record declaration on
And configured where the documents should be declared from
And configured the maximum number of documents to declare
When the benchmark driver is executed
Then documents are declared from anywhere within the specified folders and any of their sub-folders
And only the specified number of documents is declared
Sizing video:
https://ts.alfresco.com/share/s/tgcd-IoNQFCgHJ1NvFeRmw
- Depended on by
-
RM-4183 Extend IG API Benchmark Driver to file unfiled records
- Done
1.
|
Implement Benchmark Driver Extension |
|
Done | Unassigned |
|
||||||
2.
|
Test Benchmark Driver Extension |
|
Done | Unassigned |
|
||||||
3.
|
Exploratory Testing |
|
Done | Unassigned |
|
||||||
4.
|
Declaring more than 2 records at the same time fails |
|
Done | Unassigned | |||||||
5.
|
Implement create site request in TAS |
|
Done | Unassigned | |||||||
6.
|
Update Benchmark documentation on TS |
|
Done | Unassigned | |||||||
7.
|
DeclareInPlace records fails when additional files need to be created into a specific folder |
|
Done | Unassigned | |||||||
8.
|
If Record Declaration Limit is 0 or unset then none of the files from the collaboration site is declared as record |
|
Done | Unassigned | |||||||
9.
|
Configuration option should be updated |
|
Done | Unassigned | |||||||
10.
|
Documents are scheduled for more than one time to be declared as record |
|
Done | Unassigned |