Module 5’s basic workflow is test and evaluate. This is really the workhorse workflow and we’re going to spend two different modules on this workflow.
If we think about this module itself, what we’re going to focus on are the primary types/styles of functional testing. The next module we’re going to focus on problems reports, change requests.
Then within the workflow itself, basically the point of the workflow is to look at the breadth and depth of testing and how it’s done.
And, so in each cycle of testing you have a build, you take that build and you subject it to a bunch of tests and you’re trying to figure out what’s wrong with that software and how we can talk about it in ways that might get it fixed.
So there are a variety of test activities that you look at in rough, basically you’re defining tests, running tests, finding problems, logging problems, and advocating quality.
And the usual cast of characters are doing all the activities. I have those activities defined and characters defined in the notes. They produce the predictable kinds of artifacts that are also defined in the notes like test results, a summary of what actually happened during testing, test data the data you use to feed the test cases, test cases themselves, this is what we mean and how we define the stuff that we do against the program one piece at a time to find bugs, and … You can go to RUP itself to get more detail but we talk about test cases.