1. Moving into the Testing Phase Revised for October 22, 2008

2. What will you know at the end of this presentation?  Testing strategy  Testing terminology  Testing timing  Testing tools

3. What is the high level strategy for testing?  Start with Unit Testing Traverse each line of code at least once Traverse each line of code at least once Traverse each category of setup at least once Traverse each category of setup at least once Includes extension testing where possible Includes extension testing where possible Increasingly includes conversion testing Increasingly includes conversion testing  Move into Modular System Testing More Business Process Focused More Business Process Focused Includes extensions, conversions, security Includes extensions, conversions, security Processing within a module Processing within a module  System Integration Testing  Performance Testing

4. Definitions, page 1  Test Plan: An overall plan that describes how a given business process or CEMLI will be tested. A test plan includes a strategy statement, a test script and a test suite, which consists of many test cases.  Test Script: Step-by-step instructions that a functional or technical person can follow to execute a test plan/test suite.  Test Case: Individual test scenarios that together make up a test suite. For instance, a test suite to test enrollment might include several test cases, such as an international student enrollment, a returning student enrollment, a summer enrollment, etc. Each of these specific scenarios is a test case.  Test Suite: A collection of test cases intended to test all of the different possible scenarios for the process or object being tested.

5. Definitions, Page 2  Negative Testing: An extremely important aspect of thorough testing. Negative testing is the process of deliberately including data or processes that do not match what the system expects. This could be missing data, incorrect data, combinations of data that don’t make sense, data entered out of order, etc. Negative testing has two related goals: The first goal is to make sure the CEMLI is designed to handle missing or incorrect data, rather than accepting it and causing problems later in the business process – for example, it might prompt the user to enter a correct date if it encounters a bad date. The first goal is to make sure the CEMLI is designed to handle missing or incorrect data, rather than accepting it and causing problems later in the business process – for example, it might prompt the user to enter a correct date if it encounters a bad date. The second goal is to verify that the CEMLI will not crash the business process if it encounters missing or incorrect data. Instead, it generates an error indicating what is wrong and what needs to be done to correct the problem. The second goal is to verify that the CEMLI will not crash the business process if it encounters missing or incorrect data. Instead, it generates an error indicating what is wrong and what needs to be done to correct the problem.

6. Definitions, Page 3  Migration: Act of moving an object or a configuration from one instance to another.  On-line object: A type of PeopleSoft object that is managed via meta-data. It is a type of data in the instance that is “called” by the Application Server and used in PS processing. It is created or modified in Application Designer and is discoverable in compare reports and change assistant. PeopleCode, Application Engines, iScripts are examples of on-line objects.  Batch object: A type of PS object that is not managed via meta- data. It is not discoverable in compare reports. COBOL,Crystal reports and SQR are examples of batch objects. Sometimes Process Scheduler is used to manage these objects.

7. Definitions, Page 4  Refresh: The act of renewing an instance from another instance. Because code in PS is also held in the DB (meta-data) a refresh generally renews ALL data and code lines. To ensure preservation of work in progress, developers can “save off” a project of WiP and reapply it post refresh.  Instance: A self-contained environment that holds a version of PS. Development, Prototyping, Testing, Conversion, etc. activities are all held in different instances.  Validation: Refers to confirming a complete refresh and instance availability.

8. Definitions, Page 5  Unit Test: Rule is that you must traverse each code line at least once, exercise each type of configuration at least once, and test the main business processes.  Modular Testing: Builds on the above. Perform more explicit testing of configuration combinations, test all pieces of a business process, and introduce negative testing.  System Integration Testing: Builds on the above. Use common test cases throughout the entire cycle, across modules. Includes all conversions, extensions, and configurations (including security). Will include integrations with other systems. May occur in two phases.

9. Definitions, Page 6  Usability Evaluation: Task based usability ensures that the target audience is able to complete the intended function without training or extensive documentation and with a high degree of confidence.  Performance Testing: Rigorous simulation of real-world load to ensure appropriate response times and capacity.

10. Definitions, Page 7  Bug Tracking: A system and a process for documenting the things that are wrong with code, BP documentation, configurations, or security. The system will be Jira, and will be more extensive than simply an email. Detailed stats must be available for management and reporting purposes. As we approach the start of testing, an orientation process will occur.

11. So, what was the timing as of 9/8/08?

12. What is the new timing?

13. What are the tools we are using?  You’ve been using them already: The BPD and UPK content are the starting point.  Test scripts build on the foundation already present in UPK. They need to be step-by-step instructions, with a clearly visible designator for variable data (e.g. the CUNY script)  Test Cases documentation: Will be in Excel because will enable appropriate automation of testing or data loading later in the cycle. For each piece of variable data in a script, your Spreadsheet must have a corresponding value.

14. Where will we store all of this documentation?  We will use SharePoint as the primary repository.

15. What is UPK?  The User Productivity Kit (UPK) is an advanced screen capture tool that will assist with the rollout of the Campus Solutions system.  UPK can help with creation of critical documentation, training, and support materials. UPK provides business process documentation, instructor manual, job aids, training materials, and an interactive content media player.

16. UPK’s 9 Forms of Output Document Outputs 1. Business Process Document 2. Testing Document 3. Job Aid 4. Training Guide 5. Instructor Manual Interactive Modes 1. See It Mode 2. Try It Mode 3. Know It Mode 4. Do It Mode

17. See It! Allows you to watch a demonstration of a specific process--changing a name or searching for a course, for example. See It! Allows you to watch a demonstration of a specific process--changing a name or searching for a course, for example. Watch and Learn

18. Try It! Walks you through the process by showing you each mouse click or keystroke you should make, and you do the clicking and the keyboarding.

19. Know It! Tests the users on how well they know the processes and scores are generated. See It!, Try It! and Know It? are simulations that work from the UPK database; you cannot mess up anything that's "live' in PeopleSoft. See It!, Try It! and Know It? are simulations that work from the UPK database; you cannot mess up anything that's "live' in PeopleSoft.

20. Do It! Lets users do the actual transaction in an Oracle screen. Do It! will open a small window alongside the PeopleSoft page on which you are working. It will show you the next step you should take in the process you're trying to complete. Lets users do the actual transaction in an Oracle screen. Do It! will open a small window alongside the PeopleSoft page on which you are working. It will show you the next step you should take in the process you're trying to complete.

21. What did we cover?  Strategy  Terminology  Timing  Tools

22. Questions?