## Action

= Action Prepare Release Test for De Danske Aviser =



## The persons assigned to the action

 Assigned:: PKO+JRG



## The persons that previously worked on this action

 Prev assigned::



## The tasks from the WBS that are adressed by this action

 Tasks adressed:: [[Collection]]



## The time estimated for this action, Use the format Xmd, to indicate the number of man-days estimated

 Time estimated:: 4 md (pairwork)



## The time used for this action so far. Same format as Time estimated

 Time used:: 3.5 md



## The priority of this action. 1-9

 Priority:: 2



## The status of this action, legal values are 'Not described', 'Not started', 'In progress' and 'Finished'

 Status:: Finished



## The iteration that this actions belongs to

 Iteration:: 17



## Notes about this action, that should be viewable on other pages

 Notes:: 





## Detailed description of wanted output from the work to be carried out.

## E.g. Implement a utility class for writing data to a disk. The data must be base64 encoded before being written.


Prepare release test (describing what should be checked, and what the success criteria are).

Structure of the release test may be inspired by release tests for the MiniDOMS for Aarbog - iterations 5,...,7. For example the
[[Iteration7ReleaseTest|release test of iteration 7]].

<<BR>>

---

<<BR>>

The definition of the steps in the release test is located [[ActionDDAReleaseTest|here]].

In defining the release test, we still need to take care of the following.

 * (DONE) Choose which objects will be tested with, and specify at "INSERT INFO HERE" on [[ActionDDAReleaseTest|this page]]. (PKO)

 * (DONE) Choose when to
   "Craft guaranteed valid FoxML objects for those objects chosen for testing."
   (sometime before the actual release test) and place it in the [[MiniDOMSWithDDAOverview|über action-list]]. (JRG)

 * (DONE) Choose which failing cases the failure tests should address.

 * (DONE) Plan the overall steps for the success test and each failure test. Make tables listing these steps.

 * (POSTPONED TO LATER ACTION) Specify the success test in more detail (as in iteration 7 release test).

 * (POSTPONED TO LATER ACTION) Specify each failure test in detail (as in iteration 7 release test).

 * (POSTPONED TO LATER ACTION) Estimate time for running the release test.


<<BR>>

== Checklist For Working On An Action ==



The Life Cycle of an Action:
 * ''Assign people for action definition'': Done at start of iteration status meeting. Fill out '''Assigned'''
 * ''Define the action'': Describe information about what is to be done and how. Fill out '''Tasks Addressed''' and '''Time Estimated'''.
 * ''Review the definition'': Get another project group member to review the action definition, and update it.
 * ''Assign people for action implementation'': Done by project manager, usually the same persons who wrote the definition. Fill out '''Assigned''' and '''Prev assigned''' if new persons are assigned.
 * ''Implement the action'': See details below
 * ''Review the action'': Get another project group member to review what is implemented (code and documentation), and update it.
 * ''Finish the action'': Change the status to "Finished" and update the "time used" field on the action page.

Please make sure that you address the below issues, when working on an action:



 * Update the state of the action to "In Progress" when you start working on it.

 * Check if the tasks addressed by this action have their status set to "In Progress". If that is not the case, then change the state of them.

 * Keep track of how much time that has been spent working on the action. If it addresses more than one task, then make a note on the action page about how much of the elapsed time that has been spent on the individual tasks. '''Hint:''' Continually updating the "Time used" field will make it easier for you.

 * Update the "Progress History" and documentation pages of each task addressed by this action when appropriate. This depends on the situation, but in general, the task pages should hold all important related information about the work done, experiences gathered, identified requirements and so on.