-
-
Notifications
You must be signed in to change notification settings - Fork 41
Overall Protocol for Testing
John Pellman edited this page Nov 9, 2016
·
16 revisions
Before a new release can occur it must:
- Regression tests must be run using the benchmark dataset.
- Set output directory to '/tdata/CPAC/v
version number with no periods/output/benchmark. - Set working directory to '/tdata/CPAC/v
version number with no periods/working/benchmark. - Set crash directory to '/tdata/CPAC/v
version number with no periods/crash/benchmark. - Set logs directory to '/tdata/CPAC/v
version number with no periods/logs/benchmark. - Save the results for the last regression test for use in the benchmark package.
- Question: Could we run this in Docker using a modified Dockerfile for the C-PAC BIDS app?
- Unit tests must all pass.
- GUI testing must be finished with no failures.
- C-PAC must be run on novel datasets to determine if any anomalies occur with non-benchmark data:
- Perform a run on:
- Rhyme Judgement
- Serial Scanning
- Brain Genomics Superstruct Project
- Pipelines should be configured to use the following directories:
- Output directory : '/tdata/CPAC/v
version number with no periods/output/dataset name. - Working directory : '/tdata/CPAC/v
version number with no periods/working/dataset name. - Crash directory : '/tdata/CPAC/v
version number with no periods/crash/dataset name. - Logs directory : '/tdata/CPAC/v
version number with no periods/logs/dataset name.
2023+ Additions
- Developer Info
- Developers' Logbook
Legacy Posts
- Specifications
- Group Analysis Datagrabber
- Multisite and Multiscan Support
- Documentation
- Documentation Standards
- Generating Webpage Documentation with Sphinx
- How to Document Code
- Testing
- Overall Protocol for Testing
- Protocol for Testing the GUI
- Protocol for Writing Test Scripts
- Pre-Release
- Updates Checklist
- New Dependencies to Installation Instruction