How-to Submit a Software Mini-Test PlanTo schedule testing time on the Wednesday software day please send a mini-test plan to the mcc e-log. You can do this by sending email to controls-software-release mailing list as follows: Please tag your email subject line "SW Mini-Test Plan: <whatever you're doing>" The body of the email should include:
If you have changed any parameters of the system, return those system parameters to the state that you found them in, and let the program deputy know that you are finished with your test. If you need assistance returning the system to its original state, please ask the program deputy for assistance. This assumes that you have notified the program deputy, prior to your test so that system parameters have been saved before you started your test. After you finish testing. Find you mcc-elog entry and select "FOLLOW UP" link, to enter the results of your test.
Your mini-test plan should be submitted by Tuesday noon. Please note that your test/release must be APPROVED, which means that it MUST be listed on the Before starting your test you MUST:
|
How to Submit a Software Test Plan (beginning July 5 2011)Before the Day of Your Test
To schedule software testing time in production, please create a CATER Software Job. Do this by Friday noon of the week before you intend to do your work. If a CATER entry does not already exist for this work, first create a new Software Request in CATER and add the job to it. Fill out all the required and appropriate fields for the job following these guidelines: Status: Active: For new, upcoming, and in-progress jobs Complete: For jobs that have been completed or backed out Drop: For jobs that will not be performed after all Job Title: Functional description of software release or test. Intended to be brief and clear description for physicists, operators, and anyone else not doing the work. Examples: "Oracle security patch" "Add support for waveforms to SCORE" "Bug fix for EDM byte widget" "Update undulator polynomials" Resource: Name of the person doing the work Time Needed: Duration of test (hours) Time Comment (optional): Any additional comment regarding the Time Needed, for example "1 hour invasive, 2 hours non-invasive" Planned Start Date & Time: This will be updated by the Controls Deputy Beam Requirements: What conditions you require to do your test, for example beam timing, etc. Select from drop-down menu Beam Comment (optional): Any additional comment regarding the Beam Requirements, for example "Beam required through BSY" Invasive: Is your test somehow invasive to accelerator operation (interrupts beam, timing, RF, etc.). Select Yes or No from drop-down menu Invasive Comment (optional): Any additional comment regarding the Invasive field, for example "Interrupts LI25 RF stations" Scheduling Priority: Select from drop-down menu. Most often, you will choose one of these: PAMM (Planned Accessible Machine Maintenance): Work while accelerator operating (similar to Machine Development days) POMM: Planned Operational Machine Maintenance: Work while accelerator not operating (similar to Repair Opportunity Days) Description: A description of the software you are testing Test Plan: The steps you intend to take in testing your software, including any checkout Backout Plan: The steps required to back out the software Risk/Benefit: A brief description of the risk of your test (if it does not work, what is the potential fallout) and the benefit (why are you doing this) Dependencies: Other software work that your test depends on Followup Comments: Fill this field in when you have completed your job (or backed out or cancelled it) On the Day of Your TestBefore starting your test you MUST:
|