Tuesday, 4 October 2011

Workflow is the procedure technique in software testing through routing a record by all possible paths. These tests are executed to insure that all workflow activity accurately reflects the business procedure.
You test your workflow procedure in a test atmosphere by routing a record through all possible paths. Execute these tests before you export your activities to your production atmosphere to ensure that all workflow procedures accurately reflect your business activity.

Workflow Testing Process:
1.       Understands the business workflow.
2.       Develop test scripts using several techniques (decision table, use case, etc.).
3.       Verify the flow to several of user types (through - Admin, View Update user and etc.).
4.       Performs positive or negative tests.
5.       Compare the expected & actual results or log defects.
6.       Set defects & deploy.

Purpose of workflow:

Verify the outcome from implementation through testing all build
1.       Plans the test in all iteration.
2.       Integration tests for each build within the iteration.
3.       System tests for the complete of the iteration.

Design & implement tests via creating
1.       Test cases that are determine what to test?
2.       Test activity that specify how to done the tests?
3.       Runnable test elements to automate the tests.

1.       Workflow process testing
Design your test surround so that it is a copy of your production of surround. Your test d/b must admit enough information and users so that you can exhaustively test all workflow activity.
2.       Validating workflow processes
You must validate the workflow activity and to verify the architectural integrity of the procedure.
3.       Enabling workflow processes
Workflow procedure records are in a draft and a development stage until you enable the record. Enabling an activity involves validating the structure of the procedure.
4.       Activating workflow processes
You activate the workflow records before they can be expelled into a workflow processes.
5.       Disabling the workflow activities
Crippling processes keeps new records from start routed into workflow activity. Disabling processes does not affect to the records that are under control of the processes.
6.       Viewing workflow history
You can display a list of each user-initiated action in the workflow activity.
 For example, routing a record into a workflow activity, and completing an assignment.
7.       Viewing workflow assignments from a Workflow-enabled application
The Workflow map displays a graphics of a workflow activity, including its nodes or connection lines. The current place of the map in a procedure is highlighted through a box around the node. You can see the workflow duty for a record from within a workflow enabled application. You can use the Workflow map to show where your actions fall in the context of the workflow activity as a whole.
8.       Viewing a Workflow Map
The Workflow map shows a graphics of a workflow activity. You can use the Workflow map to display where your actions fall in the context of the activities as a whole.

Testing to Quick test includes the few main steps:
1.        Analyzing Your Application
Before you start creating a test, you want to analyze your application & determine your testing requirements. You need to: Determine the development surrounds in which your application handles were created, such as Java, Web, and .NET, so that you can load the needed Quick test add-ins.
Each activity should emulate a process that a clients may be perform when using your application. As you plan, try to hold the amount of steps you plan to include in all actions to a minimum. Making small, modular activity helps to make your tests easy to read, maintain and, follow.

2.       Preparing the Testing Infrastructure
At this step you also required to configure Quick test according to your testing requirements. This can involve setting up your global testing preferences, your executed session preferences, any test particular preferences, & recovery scenarios. You can also develop automation scripts that automatically fix the needed configurations on the quick test customer at the starting of an executed sessions. When you make your tests, you insert calls to one and more of the processes stored in this repository.

3.        Adding Steps to Your Actions
In this step, you add steps to the process in your test activity repository. Before you start adding steps, make sure that you link your function libraries & recovery scenarios with the related tests, so that you can insert steps using keywords.
You can develop steps using the keyword driven functionality present in the table like, graphical Keyword show or you can use the Expert View, if you choose to program steps directly in the VBScript. 

4.       Enhancing Your Test
You can get the testing process through modifying your test with some special testing options or with programming sentences, such as: Input the checkpoints & output values into your test.
A checkpoint checks particular properties and other characteristics of an object or enables you to identify whether and not your application is functioning rightly. For more data, display Checkpoints Overview.
When you use information table parameters, Quick test uses the values different from a row in the information table for all iteration of the test and action. For viewing various data, displays the Parameterizing Values.

5.       Running and Debugging Your Test
After you making your test, you can perform different types of executions to achieve different objectives.
Execute your test to debug it. You can handle your execution session to help you identify& eliminate the defects in your test. You can use the Steps Into, Step Over, or Step Out commands to execute your test step to step. You can start your executed session from a specific step in your test, and runs the test until a particular step is achieved.
Execute your test to check your application. The test begin running from the starting line in your test & stops at the last of the test. While executing, Quick test connects to your application or performs all of operation in your test, involving any checkpoints, such as the checking any text strings, tables, objects & so forth

6.        Analyzing Run Results and Reporting Defects
After you execute your test, you can view the outcomes of the run in the “Run Results Viewer”. You can see a summary of your outcome as well as an explained report. If you captured still images and movies of your application during the execution, you can see these from the “Screen Recorder” tab of the “Run Results Viewer”.


Post a Comment

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter