Posts

Retesting vs Regression Testing ( Difference between retesting and regression testing )

Retesting: Retesting is functional testing type In this type of testing, the tester re tests the application which was earlier reported as a bug and now fixed by the developer. This bug can be due to functionality issues as well as design issues. Retesting the functionality of a link which was previously not working or testing the link accessibility issues of a page etc can be listed as examples for retesting. Regression testing: Regression is a testing of the unchanged area of software or application to ensure working with new changes.Regression testing is done to test whether the changes made on the site have any impact on other modules which were earlier working fine. New requirement change, implementation of new functionality are some of the scenarios where regression testing is effective. Regression testing can be automated using effective automated tools such as Selenium, Quick Test Professional etc.

The tester should have skill

The tester should have skill A destructive Mindset to crack or crash system under test frequently Bring bad news Under worst time pressure  Need to take a different view, a different mindset  How should fault information be communicated 

Why Testing is Necessary

Why Testing i s Necessary  Build confidence on Software or application  Demonstrate conformance to requirements find faults for the best experience of the user Reduce costs Show system meets user needs Assess the software quality

Test Analysis & Design ( What is Test case )

Test Analysis & Design Test Case Fundamentals What is Test case definition? A test case is a document, which has a set of test data, prerequisite conditions, expected results, developed for a particular test condition in order to verify output against a given requirement. The process of developing test cases can also help find problems in the requirements, architecture or design of software. Test Case Template A test case can have the following elements. Note, however, that normally a test management tool is used by companies and the format is determined by the tool used, this is basic format use when writing test cases from excel tool. Test scenario ID The ID of the test scenario to which this test case belongs<High-level test case belongs to which module>. Test Case ID The ID of the test case. Test Case Description The description/objective of the test case. Prerequisites Any p...

What is Test case

A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of Creating test cases can also help find problems in the requirements or design of a Software. Test Case Format Test scenario id test case id test  case Summary Related Requirement Prerequisites Test Procedure Test Data Expected Result Actual Result Status Comment Created By execution Date Tester Test Environment

TEST PLAN TEMPLATE IEEE 829

TEST PLAN TEMPLATE IEEE 829 1) Test Plan Identifier 2) References 3) Introduction 4) Test Items 5) Software Risk Issues 6) Features to be Tested 7) Features not to be Tested 8) Approach 9) Item Pass/Fail Criteria 10) Suspension Criteria and Resumption Requirements 11)  Test Deliverables 12) Remaining Test Tasks 13) Environmental Needs 14) Staffing and Training Needs 15) Responsibilities 16) Schedule 17) Planning Risks and Contingencies 18) Approvals 19) Glossary

Priority vs Severity

High Severity – High Priority bug This is when major path through the application is broken, for example, on an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error of page not found. High Severity – Low Priority bug This happens when the bug causes major problems, but it only happens in very rare conditions or situations, for example, customers who use very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very old version, it is not a high priority to fix the issue. High Priority – Low Severity bug The logo or name of the company is not displayed on the website. It is important to fix the issue as soon as possible, although it may not create cause a System and other component. Low Priority – Low Severity bug The privacy policy page take a long time to load. Not many people view the privacy policy page and slow...