Jetstream+Testing+Step-by-Step+GIT+Commands

The following steps describe the testing procedure for the Jetstream group update.


 * 1) If you are a member of the current merge group, please disregard steps 2 - 4 that describe creating a new branch for testing. Instead, start at step 5 and use your merge branch as the testing branch, i.e. pull one more time from the sync staging area to the branch you just used for merging. This will avoid you having to redo any conflict resolution that you may have already done. You may still encounter conflicts depending on commits made to the sync staging area after your pull during the merge process.
 * 2) Commit any pending changes to your master branch before beginning the testing process:
 * git checkout master
 * git commit -a
 * 1) Create a branch for testing:
 * git branch 
 * 1) Switch to the testing branch so that your local master branch is not affected during testing/debugging:
 * git checkout 
 * 1) Pull from the Jetstream sync staging area:
 * git pull /home/z/zingg/treist/jetstream_sync_staging_
 * 1) Resolve conflicts
 * 2) Execute the following script to compile Jetstream:
 * ./make_jetstream
 * 1) Find out what test case(s) you are running:
 * Go to the ‘Test Case Details’ tab on Jetstream Test Suite Google Doc spreadsheet. The spreadsheet can be found [|__here__].
 * Look for your name under the ‘Test Case Owner’ column and note the corresponding test case number(s)
 * 1) Copy the test case folder(s) from the Jetstream Test Suite directory on Scinet to your working directory:
 * cp -d -r /project/z/zingg/jetstream_testSuite/### /scratch/z/zingg//###
 * ***NOTE: the ‘-d’ in the above cp command is required to copy only the symbolic links to the grid files and not the actual grid files
 * 1) Run the test case by submitting the script contained in the test case folder to the Scinet queue:
 * qsub sciSubmit
 * 1) After the test case has run, compare the results to the benchmark values for your test case found in the corresponding tab on the Jetstream Test Suite Google Doc spreadsheet:
 * Look for the tabs at the bottom of the spreadsheet named JSTS ### Benchmarks
 * 1) Update the ‘Test Case Details’ tab on Jetstream Test Suite Google Doc spreadsheet:
 * Update the ‘Test Case Run Date’ column
 * Update the ‘PASS/FAIL’ column
 * If the test case passed, then your testing task is complete. Otherwise, commence debugging
 * 1) Debug test case as required:
 * Commit bug fixes to your jsts_testing branch
 * Push bug fixes to the Jetstream sync staging area:
 * git push /home/z/zingg/treist/jetstream_sync_staging_ :master
 * 1) Send the gatekeeper (Tom) an email when you are finished testing.