Test Long and Prosper

1. Test Longand Prosper presented by Janet Gray July 26, 2005

2. Seek out New Life and New civilizations • The STARS Testing Team will manage testing, validation, and documentation of the functional & technical requirements in the following areas: • Set up tables • Self-Service • Reporting • Batch processes • Security • Business Processes • Modifications and Interfaces

3. When logic fails, trust a hunch Testing Goals • Test all modifications, interfaces, data delivery and business processes • Test all PS components & self-service with Cornell defined data , including load/stress testing and system testing • Validate all set up & security • Determine errors, report errors for resolution prior to implementation • Document all information relative to the each specific project

4. Humans are highly illogical Assumptions • User/SME will be responsible for all test script & scenario development • Tools, resources (inc. tech support) & infrastructure available throughout implementation, fixes and upgrades • Necessary project team members will assist in problem resolution • All areas to be tested have been defined, developed & unit tested

5. Keep your phaser set to stun Requirements • STARS test environment & instance will be kept up-to-date with all upgrades, setup tables, & patches • Conversion & test data will be reloaded “by request” after any refresh • STARS test environment should be close to production as possible

6. Don’t put all your ranking officers in one shuttlecraft Testing Lead Duties • Develop testing plans • Prepare testing guidelines, procedures, & templates • Set up TestDirector for testing management • Set up tests & error reporting workflow • Monitor progress of testing plans & advise Project Manager of any slippage

7. Don’t put all your ranking officers in one shuttlecraftcontinued • Coordinate with other modules for execution of testing across modules • Work with Project Manager & Tech Lead on test plan tasks • Coordinate with CIT Technical Manager the refresh of SATest Testing Lead Duties

8. Infinite Diversity in Infinite Combinations (IDIC) Testing Designer/Tester Duties • Create QuickTest Pro scripts • Use TestDirector to document test results & problems, & testing management • Develop test design for functional & performance testing • Create & document test cases & data • Coordinate testing activities with CIT, functional area & other modules

9. Infinite Diversity in Infinite Combinations (IDIC)continued • Document test results & report problems to Implementation Manager • Schedule re-execution of tests on problems

10. If it can’t be fixed, ask Scotty Tech, Security, Setup Tables Support Duties • Maintain infrastructure • Provide tech support for testing tools • Direct updates & fixes to database • Set up & apply security roles • Assist in remediation of errors found • Set up & apply set up tables necessary for testing

11. There’s no such thing as a Vulcan death grip Developer Duties • Perform unit testing • Troubleshoot problems arising from testing • Communicate unit testing progress to Test Lead • Work with Testing Lead on data validation planning & testing efforts

12. Even in our world, sometimes we are aliens • Compare & validate data between legacy systems & Oracle PeopleSoft • Report any errors to Testing Lead Conversion Validator Duties

13. Having is not so pleasing a thing as wanting, it is not logical but it is often true • Provide subject matter expertise for testing • Write test scripts used to create test steps in TestDirector Subject Matter Experts Duties

14. Logic is the beginning of wisdom; not the end • Unit Test • Test and validate individual pieces of software function as a “stand alone” unit. • Implementation at module level defect free • Verifies mods, interfaces or reports meet functional & technical requirements as outlined in the To-Be Process • User and developers work closely together before, during and after unit testing to ensure all the requirements are met.

15. Logic is the beginning of wisdom; not the endcontinued • Integration Testing • Using top-down method • Determines if software operates properly as each subprocess is added • Individual software tested & combined with other software, making sure all data, data sharing & links are working as specified

16. Logic is the beginning of wisdom; not the endcontinued • Completed after integrated processes have be successfully tested • Whole System environment test System Testing

17. Logic is the beginning of wisdom; not the endcontinued • Load testing will test an application against a number of users • Stress testing is load testing over an extended period of time for validation purposes Load/Stress Testing

18. You will be assimilated Quality Assurance Testing • All the organization standards have been followed • A check to see all original requirements have been documented & proper system implementation of those requirements

19. Resistance is Futile • User tests the software • Must be involved in the beginning with Oracle PeopleSoft functionality • Gain understanding how functionality fits with their business needs User Acceptance Testing

20. You do remember how to fire phasers? • Re-running of successfully executed test cases to detect failures spawned by changes or corrections made during software development & maintenance Regression Testing

21. Computer, compute to the last digit the value of pi TestDirector Definitions • Test Case • A documented procedure verifying a system requirement (a test scenario) • Test Step • Use To-Be process “functional test scripts” for either manual or automated testing • Automated Test Script • Use when there are multiple data values for the same operation

22. Enemies are often invisible – like Klingons, they can be cloaked • Data Validation from Conversion • Business Processes • PS Delivered Reporting • Interfaces • Modifications • Cross-Functional Areas Items to be Tested

23. Enemies are often invisible – like Klingons, they can be cloakedcontinued • RDS Canned Reports • RDS Testing • Load Testing • Stress Testing • Security Testing • Platform Testing Items to be Tested

24. Insufficient data does not compute Testing Tools • TestDirector • Monitor test development, progress & defect reporting • Document & run tests • LoadRunner • Run load tests • QuickTest Pro • Create & run automated testing

25. Boldly go where no man has gone before

26. Questions?