Pages

Sunday, June 6, 2010

Quality Center

What is Quality Center?

It is a comprehensive Web-Based Test Management tool supports high-level of communication and association among various stakeholders(BA's Developers,Testers...)

What can be integrated with QC?

QTP.WinRunner,LoadRunner are few of them to be integrated with QC.

Difference between Retesting and Regression Testing

Retesting is done to validate for the particular fix in a build.

Regression is done to validate for the correctness which may have impacted due to fix in other module/ component.... .it is applicable also to that module where the errors have come.

Hence regression is part of retesting, which may have caused due to fix... 

Retesting is a subset of regression where we test those failed testcases.

Regression is the whole set where we test all the testcases

Testcase History

What is a Test Case?
The step by step process to be followed to the application correctness as per requirement.

From where Test Cases are Derived?
Test Cases are derived from Usecases and mostly from Requirements Docs.

Who is responsible for Test Cases?
Test Engineer

Where Test Cases are Documented?
In MS-Word/MS-Excel.

Qualities of a good Test Case?
The following are the qualities of a good Test Case

  1. Simple,Clear,Unique.
  2. Proper Start and End
  3. Follow naming convention
  4. Consistent and Documented
  5. Should have standard template
  6. Traceble for Requirement
  7. No gaps and missing links

Types of Test Cases
1.User Interface:-To check user interfaces of an application
Eg:-Font Align,Color,Spelling

2.Useablity:-To check user freindliness of an application
Eg:-Default cursor focus,Alt+Tab,Oouse-over

3.Validation:-To check field validation
Eg:-TextBox,CheckBox,Radio Button.

4.Functional:-To check functional validation
Eg:-Hyperlinks,Images,Buttons

Test Case Template

  1. Project
  2. Module
  3. Created By
  4. Created On
  5. Reviewed By
  6. Reviewed On
  7. Documents Reffered
  8. TestCase Name
  9. TestCase Description
  10. Stepname
  11. TestData
  12. StepDescription
  13. Excepted result
  14. Priority
  15. Review Comments
  16. Actual Results
  17. Executed By
  18. Executed On
  19. Status
  20. Build Version
  21. Defect-ID
  22. Defect Priority

Conditions for Automation Testing when and why we go for Automation

When we go for automation testing :


  1. When we find that the project has more no of releases which requires regression testing then automation is useful.
  2. Useful for sanity/smoke testing when there is a frequent release of build in to production.



Why we go for automation testing:


  1. It provides more coverage of regression testing.
  2. Reduces time for testing and there by helps your product for faster relase intp the market 3.Improves productivity of the product.
  3. Improves the re-usability of tests.
  4. Provides a detailed test log.



Conditions before going into automation 


  1. One Round of Manual Testing should be mandatory done.
  2. Build should be stable.

Risk Factors with time constraints in Manual Testing

Most of the times it is not possible to test the whole application within the specified time. In such situations it’s better to find out the risk factors in the projects and concentrate on them.

Here are some points to be considered when you are in such a situation:
1) Find out Important functionality in your project?
2) Find out High-risk module of the project?
3) Which functionality has the largest financial impact on users?
4) Which aspects of the application are most important to the customer?
5) Which parts of the code are most complex, and thus most subject to errors?
6) What do the developers think are the highest-risk aspects of the application?
7) What kinds of problems would cause the most customer service complaints?
8) What kinds of tests could easily cover multiple functionalities?