Subscribe by Email


Showing posts with label Test Manager. Show all posts
Showing posts with label Test Manager. Show all posts

Saturday, October 6, 2012

How do u do batch testing in WinRunner & Is it possible to do in QTP, if so explain?


WinRunner provides you the facility of executing a certain batch of the unattended tests. This feature of the winrunner has proved to be quite useful especially in the situations when a large groups of tests have to be run over night i.e., an over night run. 

How to do batch testing in WinRunner?

- A batch test can be viewed as a test consisting of a test script which holds the calls to the other tests. 
- Such call statements execute each and every test called in the list and also save the result up on execution.
- A batch test may consist of n number of tests depending up on the need and requirement of the user. 
- A batch as such just seems like a normal test but with an unusual large number of calls. 
- A batch test can be run by using the option “run in batch mode”. 
- This option is available in the run category of the general dialog box which gets invoke just before the start of the execution of the test. 
- Whenever a test is run in batch mode, all of the messages that may be displayed during the test run are suppressed by the winrunner. 
- This is done so that the winrunner is able to run a batch test unattended. 
- The execution of the batch tests is therefore different from the regular, interactive test runs where you may come across several messages popping up on the screen. 
- In batch tests, this thing is not there and so a lot of time is saved. 
- The current chain of all the called tests can be viewed at a break point in the call chain pane available for viewing in the debug viewer window. 
- After the completion of the batch test run the winrunner makes the results available in the test results window. 
- Winrunner provides you the facility of running the batch test via command line.

Is it possible to do batch testing through QTP?

- The quick test professional is the successor of the winrunner and is quite advanced and efficient in many respects as compared to the winrunner. 
- Batch testing is possible in quick test professional. 
Difference lies in the way in which the batch testing is carried out here. 
- The quick test professional facilitates the batch testing service with the help of a separate built-in tool called the test batch runner or QTP batch testing tool. 
With this tool you can group the tests in to a number of batches which are then executed. 
- The result of this batch test run is made available in the test result viewer. 
- In quick test professional, batch wise viewing of the result is not possible. 
Results for individual tests have to be viewed. 
- For the execution of a test batch you need to open the path of the test batch and give the run command. 
- In quick test professional, other mercury products for batch testing can also be installed and used if one is not comfortable with the in built tool of the quick test professional i.e., the test batch runner. 
- For doing this you need to follow the below mentioned sequence:
Tools menu à options à run à check the check box “allow other mercury products” à apply à ok
- Even a partial batch test is also possible! 
- You just need to deselect the tests that you want to be executed. 
- MTM or multi test manager is another mercury product using which one can carry out batch testing. 


Friday, April 27, 2012

What kinds of people are involved in software testing?


Software testing like any other process of the software development cycle is a very critical and important phase and so does it has been dedicated an entire cycle called software testing life cycle. Without software you will not have any direction in the way of software development.

The overall efficiency of the software testing depends a whole lot on the professionals or individuals performing it. This article is about the people who are involved with the software testing.

  1. Developer: A developer as the name suggests is responsible for taking care of all the development activities like:
(a)  Preparation of the test plan before the coding of the software system or application starts.
(b) Creation of the input test data as per the various software testing methodologies are to be used.
(c)  Preparation of the documentation of the expected outcomes of the different test cases.
(d) Testing the source code according to their personally developed schemas.
(e)  Documentation of the actual test results.
(f)  Validation of the code whose actual output is same as the expected outcome.
(g)  Filling up the project documentation repository with the results of the unit testing and the test data used as input.
(h)   Active participation in the process of the code reviews to ensure that the unit testing is complete.

  1. Data architect or Data Modeler: Data architect is responsible for taking care of the management of all the issues regarding the architecture and build of the software system or application:
(a)  Testing of the scripts written in data definition language (DDL) as per their personally developed schema.
(b) Filling up the project documentation repository with the tested and validate DDL scripts.

  1. Senior Developer or System Tester: A team consists of more than one senior developers or system testers and they are responsible for taking care of the actual software testing of the software system or application. They share some responsibilities with the developers:
a)  Active participation in the process of the code reviews like the developers for determining that the unit testing has been completed successfully.
b)  Preparation of the test plan
c)  Creation of the test data for input to input to test cases.
d)  Preparation of the documentation of the expected outcomes of the different test cases.
e)  Implementing the code in the testing environment
f)   Execution of the work streams that are comprised of the system tests along with their scripts.
g) Validation of the actual results of the tests.
h) Creation of the defects if required for some kinds of testing techniques like fault injection techniques, in defect management tracking tools etc.
(i)  Filling up the project documentation repository with the results of the system testing and the test data used as input.

  1. Data base Administrator: They share the responsibilities of the following tasks:
a) Creation of the system, quality assurance, release testing, user acceptance and integration environments.
b) Execution of the scripts written in DDL or data definition language and DML or data manipulation language in the environments as specified in the test plan.
c) Preparation of the restores and back ups.

  1. Integration Tester or Senior ETL Designer: They are responsible for:
(a)    Participation in the system test reviews for ensuring the completeness of the system.
(b)   Preparation of the integration test plan.
(c)    Creation of the integration test data.
(d)   Documentation of the expected outcomes of the integration test results.
(e)    Implementing code in the integration testing environment.
(f)    Validation of the actual integration test results.

  1. Quality assurance people
  2. QA software tester
  3. User acceptance tester
  4. Release manager
  5. Production support specialists


Friday, May 6, 2011

What makes a good Software Test Engineer, SQA Engineer, Test Manager?

A good software test engineer has the following qualities:
- a software engineer should focus on having a high quality product.
- a software engineer should understand customer's needs and requirements.
- a software engineer should maintain a tactful and diplomatic relationship with developers.
- a software engineer should maintain a good relationship with non technical people.
- a software engineer should be able to have a judgment skill when needed.

A good Software Quality Assurance engineer has the following qualities:
- a software quality assurance engineer should focus on having a high quality product.
- a software quality assurance engineer should understand customer's needs and requirements.
- a software quality assurance engineer should maintain a tactful and diplomatic relationship with developers.
- a software quality assurance engineer should maintain a good relationship with non technical people.
- a software quality assurance engineer should be able to have a judgment skill when needed.
- a software quality assurance engineer should have a proper understanding of software development life cycle.
- a software quality assurance engineer should understand business approach and goals.
- a software quality assurance engineer should have good communications skills.
- a software quality assurance engineer should be able to find problem areas.

A good QA/Test Manager has the following properties
- he should have a good understanding of software development life cycle.
- he should have a good and healthy relation with the technical and non technical people.
- he should be able to increase his team's productivity and efficiency.
- he should be able to create enthusiasm about work among team members.
- he should be able to make correct and quick decisions.
- he should be good at handling pressure.
- he should have diplomatic skills.


Facebook activity