test-plan/git-lite/consumer

[bwalsh]

Epic

As a release manager , I want a test script to ensure comprehensive and repeatable testing of the new feature(s).

Use case

As a testing engineer, I want a data download and replication script to facilitate efficient testing of data synchronization and replication processes.

Definition of Done:

• Test script is created and documented.
• The script is reviewed and approved by the testing team.
• optional The script is integrated into the testing process and automated frameworks.
• script is executed and all acceptance criteria are met.

Considerations

• The system should generate clear error messages for users in case of invalid data submissions, guiding them on how to correct the issues.
• It should perform thorough validation of data integrity to prevent corruption or loss during the upload process.
• Security measures should be implemented to protect against potential data breaches or unauthorized access during the submission and upload process.
• It must log relevant information, including successful uploads and any errors encountered, for auditing and debugging purposes.
• The system should be version-controlled to track changes and updates over time.
• The validation and upload process should be easily integrable into automated testing frameworks for continuous integration.

consumer test script

# Use case: As a data consumer, I will need download a project.

## test should work with or without environment variables

#export G3T_PROFILE=local
#export G3T_PROJECT_ID=ohsu-test002b
#g3t clone

unset G3T_PROJECT_ID
unset G3T_PROFILE
g3t --profile local clone --project_id ohsu-test001b

## test: the project should exist
cd ohsu-test001b
## test: the meta data should be in place with the latest changes
grep male META/Patient.ndjson |  jq '[.id, .gender]'
#"20d7d7eb-46f9-5175-b474-cb504f66e10e"
## test by default, the files should not be downloaded
ls tests
# ls: tests: No such file or directory

## Use case: I should be able to download files
g3t pull
## test directory should now contain
tree tests
#tests
#└── fixtures
#    └── dir_to_study
#        ├── file-1.txt
#        ├── file-2.csv
#        └── sub-dir
#            └── file-3.pdf
#