Test Release Candidate (Activity)

(Difference between revisions)
Jump to: navigation, search
(just sticking template in)
 
Line 2: Line 2:
 
{| border="1"
 
{| border="1"
 
|-  
 
|-  
|'''Title''' || Name of the activity
+
|'''Title''' || Release Testing
 
|-
 
|-
|'''Overview''' || High level description of what the student will do
+
|'''Overview''' || Student will test a release candidate for an open source software project and report findings.
 
|-  
 
|-  
|'''Prerequisite Knowledge''' || What topics and tools does the student need to know prior to beginning this activity?
+
|'''Prerequisite Knowledge''' || Students will probably need to use git (see the [[Git_Activity]] series).
 
|-
 
|-
|'''Learning Objectives''' || What should the student be able to do after completing completed this activity?
+
|'''Learning Objectives''' || Students will be able to (1) explain how release testing fits into the SLDC lifecycle (2) go through the steps of a release test and provide their observations (3) be able to describe (in generic terms) the steps required for release testing (3) 
 
|}
 
|}
  
Line 22: Line 22:
  
 
=== Directions: ===
 
=== Directions: ===
What should the student do?
+
1) Read about what release testing is and why it's done
 +
2) Test a release
 +
3) Write release testing instructions for a new version of a boxed cake mix
  
  

Revision as of 22:52, 7 August 2015

Title Release Testing
Overview Student will test a release candidate for an open source software project and report findings.
Prerequisite Knowledge Students will probably need to use git (see the Git_Activity series).
Learning Objectives Students will be able to (1) explain how release testing fits into the SLDC lifecycle (2) go through the steps of a release test and provide their observations (3) be able to describe (in generic terms) the steps required for release testing (3)

Background:

Is there background reading material?

Are there other activities the student should have done first?

What is the rational for this activity?

Include helpful hints to faculty here.


Directions:

1) Read about what release testing is and why it's done 2) Test a release 3) Write release testing instructions for a new version of a boxed cake mix


Deliverables:

What will the student hand in?


Assessment:

How will the activity be graded?

How will learning will be measured?

Include sample assessment questions/rubrics.

Criteria Level 1 (fail) Level 2 (pass) Level 3 (good) Level 4 (exceptional)
The purpose of the project
Why the project is open source

Comments:

What should the instructor know before using this activity?

What are some likely difficulties that an instructor may encounter using this activity?


Additional Information:

Knowledge Area/Knowledge Unit What ACM Computing Curricula 2013 knowledge area and units does this activity cover? ACM_Body_of_Knowledge
Topic What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf
Level of Difficulty Is this activity easy, medium or challenging?
Estimated Time to Completion How long should it take for the student to complete the activity?
Materials/Environment What does the student need? Internet access, IRC client, Git Hub account, LINUX machine, etc.?
Author Who wrote this activity?
Source Is there another activity on which this activity is based? If so, please provide a link to the original resource.
License Under which license is this material made available? (http://creativecommons.org/licenses/)


Suggestions to Open Source Mentors:

Suggestions for an open source community member who is working in conjunction with the instructor.



This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox