moving into the testing phase revised for october 22, 2008

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

Upload: charles-white

Post on 27-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

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

Moving into the Testing PhaseMoving into the Testing Phase

Revised for October 22, 2008Revised for October 22, 2008

Page 2: Moving into the Testing Phase Revised for October 22, 2008

What will you know at the end of this What will you know at the end of this presentation?presentation?

Testing strategyTesting strategy Testing terminologyTesting terminology Testing timingTesting timing Testing toolsTesting tools

Page 3: Moving into the Testing Phase Revised for October 22, 2008

What is the high level strategy for What is the high level strategy for testing?testing?

Start with Unit TestingStart with Unit Testing Traverse each line of code at least onceTraverse each line of code at least once Traverse each category of setup at least onceTraverse each category of setup at least once Includes extension testing where possibleIncludes extension testing where possible Increasingly includes conversion testingIncreasingly includes conversion testing

Move into Modular System TestingMove into Modular System Testing More Business Process FocusedMore Business Process Focused Includes extensions, conversions, securityIncludes extensions, conversions, security Processing within a moduleProcessing within a module

System Integration TestingSystem Integration Testing Performance TestingPerformance Testing

Page 4: Moving into the Testing Phase Revised for October 22, 2008

Definitions, page 1Definitions, page 1

Test Plan: An overall plan that describes how a given business Test Plan: An overall plan that describes how a given business process or CEMLI will be tested. A test plan includes a strategy 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 statement, a test script and a test suite, which consists of many test cases.cases.

Test Script: Step-by-step instructions that a functional or technical Test Script: Step-by-step instructions that a functional or technical person can follow to execute a test plan/test suite.person can follow to execute a test plan/test suite.

Test Case: Individual test scenarios that together make up a test Test Case: Individual test scenarios that together make up a test suite. For instance, a test suite to test enrollment might include suite. For instance, a test suite to test enrollment might include several test cases, such as an international student enrollment, a several test cases, such as an international student enrollment, a returning student enrollment, a summer enrollment, etc. Each of returning student enrollment, a summer enrollment, etc. Each of these specific scenarios is a test case.these specific scenarios is a test case.

Test Suite: A collection of test cases intended to test all of the Test Suite: A collection of test cases intended to test all of the different possible scenarios for the process or object being tested. different possible scenarios for the process or object being tested.

Page 5: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 2Definitions, Page 2 Negative Testing: An extremely important aspect of thorough testing. Negative Testing: An extremely important aspect of thorough testing.

Negative testing is the process of deliberately including data or Negative testing is the process of deliberately including data or processes that do not match what the system expects. This could be processes that do not match what the system expects. This could be missing data, incorrect data, combinations of data that don’t make missing data, incorrect data, combinations of data that don’t make sense, data entered out of order, etc. Negative testing has two related sense, data entered out of order, etc. Negative testing has two related goals:goals:

The first goal is to make sure the CEMLI is designed to handle The first goal is to make sure the CEMLI is designed to handle missing or incorrect data, rather than accepting it and causing missing or incorrect data, rather than accepting it and causing problems later in the business process – for example, it might problems later in the business process – for example, it might prompt the user to enter a correct date if it encounters a bad date.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 The second goal is to verify that the CEMLI will not crash the business process if it encounters missing or incorrect data. business process if it encounters missing or incorrect data. Instead, it generates an error indicating what is wrong and what Instead, it generates an error indicating what is wrong and what needs to be done to correct the problem.needs to be done to correct the problem.

Page 6: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 3Definitions, Page 3

Migration: Act of moving an object or a configuration from one Migration: Act of moving an object or a configuration from one instance to another.instance to another.

On-line object: A type of PeopleSoft object that is managed via 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 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 Application Server and used in PS processing. It is created or modified in Application Designer and is discoverable in compare modified in Application Designer and is discoverable in compare reports and change assistant. PeopleCode, Application Engines, reports and change assistant. PeopleCode, Application Engines, iScripts are examples of on-line objects.iScripts are examples of on-line objects.

Batch object: A type of PS object that is not managed via meta-Batch object: A type of PS object that is not managed via meta-data. It is not discoverable in compare reports. COBOL,Crystal data. It is not discoverable in compare reports. COBOL,Crystal reports and SQR are examples of batch objects. Sometimes reports and SQR are examples of batch objects. Sometimes Process Scheduler is used to manage these objects.Process Scheduler is used to manage these objects.

Page 7: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 4Definitions, Page 4

Refresh: The act of renewing an instance from another Refresh: The act of renewing an instance from another instance. Because code in PS is also held in the DB instance. Because code in PS is also held in the DB (meta-data) a refresh generally renews ALL data and (meta-data) a refresh generally renews ALL data and code lines. To ensure preservation of work in progress, code lines. To ensure preservation of work in progress, developers can “save off” a project of WiP and reapply it developers can “save off” a project of WiP and reapply it post refresh. post refresh.

Instance: A self-contained environment that holds a Instance: A self-contained environment that holds a version of PS. Development, Prototyping, Testing, version of PS. Development, Prototyping, Testing, Conversion, etc. activities are all held in different Conversion, etc. activities are all held in different instances. instances.

Validation: Refers to confirming a complete refresh and Validation: Refers to confirming a complete refresh and instance availability.instance availability.

Page 8: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 5Definitions, Page 5

Unit Test: Rule is that you must traverse each code line at Unit Test: Rule is that you must traverse each code line at least once, exercise each type of configuration at least least once, exercise each type of configuration at least once, and test the main business processes.once, and test the main business processes.

Modular Testing: Builds on the above. Perform more Modular Testing: Builds on the above. Perform more explicit testing of configuration combinations, test all pieces explicit testing of configuration combinations, test all pieces of a business process, and introduce negative testing.of a business process, and introduce negative testing.

System Integration Testing: Builds on the above. Use System Integration Testing: Builds on the above. Use common test cases throughout the entire cycle, across common test cases throughout the entire cycle, across modules. Includes all conversions, extensions, and modules. Includes all conversions, extensions, and configurations (including security). Will include integrations configurations (including security). Will include integrations with other systems. May occur in two phases.with other systems. May occur in two phases.

Page 9: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 6Definitions, Page 6

Usability Evaluation: Task based usability ensures that Usability Evaluation: Task based usability ensures that the target audience is able to complete the intended the target audience is able to complete the intended function without training or extensive documentation and function without training or extensive documentation and with a high degree of confidence.with a high degree of confidence.

Performance Testing: Rigorous simulation of real-world Performance Testing: Rigorous simulation of real-world load to ensure appropriate response times and capacity.load to ensure appropriate response times and capacity.

Page 10: Moving into the Testing Phase Revised for October 22, 2008

Definitions, Page 7Definitions, Page 7

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

Page 11: Moving into the Testing Phase Revised for October 22, 2008

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

Page 12: Moving into the Testing Phase Revised for October 22, 2008

What is the new timing?What is the new timing?

Page 13: Moving into the Testing Phase Revised for October 22, 2008

What are the tools we are using?What are the tools we are using?

You’ve been using them already: The BPD and UPK You’ve been using them already: The BPD and UPK content are the starting point.content are the starting point.

Test scripts build on the foundation already present in Test scripts build on the foundation already present in UPK. They need to be step-by-step instructions, with a UPK. They need to be step-by-step instructions, with a clearly visible designator for variable data (e.g. the clearly visible designator for variable data (e.g. the CUNY script)CUNY script)

Test Cases documentation: Will be in Excel because will Test Cases documentation: Will be in Excel because will enable appropriate automation of testing or data loading enable appropriate automation of testing or data loading later in the cycle. For each piece of variable data in a later in the cycle. For each piece of variable data in a script, your Spreadsheet must have a corresponding script, your Spreadsheet must have a corresponding value.value.

Page 14: Moving into the Testing Phase Revised for October 22, 2008

Where will we store all of this Where will we store all of this documentation?documentation?

We will use SharePoint as the primary repository. We will use SharePoint as the primary repository.

Page 15: Moving into the Testing Phase Revised for October 22, 2008

What is UPK?What is UPK?

The User Productivity Kit (UPK) is an advanced The User Productivity Kit (UPK) is an advanced screen capture tool that will assist with the screen capture tool that will assist with the rollout of the Campus Solutions system. rollout of the Campus Solutions system.

UPK can help with creation of critical UPK can help with creation of critical documentation, training, and support materials. documentation, training, and support materials. UPK provides business process documentation, UPK provides business process documentation, instructor manual, job aids, training materials, instructor manual, job aids, training materials, and an interactive content media player. and an interactive content media player.

Page 16: Moving into the Testing Phase Revised for October 22, 2008

UPK’s 9 Forms of Output UPK’s 9 Forms of Output Document OutputsDocument Outputs

1.1. Business Process Business Process Document Document

2.2. Testing Document Testing Document

3.3. Job Aid Job Aid

4.4. Training Guide Training Guide

5.5. Instructor Manual Instructor Manual

InteractiveInteractive ModesModes

1.1. See It Mode See It Mode

2.2. Try It Mode Try It Mode

3.3. Know It Mode Know It Mode

4.4. Do It ModeDo It Mode

Page 17: Moving into the Testing Phase Revised for October 22, 2008

See It!See It!

Allows you to watch a demonstration of a Allows you to watch a demonstration of a specific process--changing a name or searching specific process--changing a name or searching

for a course, for example.  for a course, for example. 

Watch and LearnWatch and Learn

Page 18: Moving into the Testing Phase Revised for October 22, 2008

Try It!Try It!

Walks you through the process by showing you Walks you through the process by showing you each mouse click or keystroke you should make, each mouse click or keystroke you should make,

and you do the clicking and the keyboarding.and you do the clicking and the keyboarding.

Page 19: Moving into the Testing Phase Revised for October 22, 2008

Know It!Know It!

Tests the users on how well they know the processes Tests the users on how well they know the processes and scores are generated.and scores are generated.

See It!, Try It! and Know It? are simulations that work See It!, Try It! and Know It? are simulations that work from the UPK database; you cannot mess up anything from the UPK database; you cannot mess up anything that's "live' in PeopleSoft. that's "live' in PeopleSoft.

Page 20: Moving into the Testing Phase Revised for October 22, 2008

Do It!Do It!

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

Page 21: Moving into the Testing Phase Revised for October 22, 2008

What did we cover?What did we cover?

StrategyStrategy TerminologyTerminology TimingTiming ToolsTools

Page 22: Moving into the Testing Phase Revised for October 22, 2008

Questions?