Author Archives: cryong

Below is a diagram that captures a typical test estimation process: Two of the most commonly used test estimation techniques are: Metric-based approach – this involves estimating the testing effort based on metrics of former or similar projects or based on typical values Expert-based approach – this involves estimating the tasks based on estimates madeContinue reading “Test Estimation Process”

Entry Criteria Entry criteria is a set of conditions or requirements, which are required to be fulfilled or achieved to start a testing actviity. Some of possible criteria are: Complete or partially testable code is available Requirements are defined and approved Availability of sufficient and desired test data Test cases are developed and ready TestContinue reading “Entry, Exit and Suspension Criteria”

There are number of test metrics that could be used to assess the quality of test execution for a project i.e. effectiveness of the testing team. The two most important ones could be: Defect leakage ratio – this refers to the number of defects that have been undetected during the project (SDLC) and ended upContinue reading “Defect rejection and leakage ratio”

Ideally, the test manager or test lead will be responsible however one of the members of the QA team may also be asked to write up the test plan document. Below are 8 activities that are involved in the process of creating a test plan document: Product and requirements analysis – this is where youContinue reading “Process to create test plan document”

API documentation is essentially a user instructions/help guidebook for an API. It tells consumers how to use the API, what the API does, expected input, expected output, relevant status codes and how to resolve errors should they occur. Good API documentation is crucial because: People will find it easier to use the API, leading toContinue reading “The importance of API documentation”

Application Programming Interfaces (APIs) are interfaces that allow communications between different systems or layers of an application. Applications often have 3 layers: a data layer (database), service layer (API/business logic), and presentation (UI) layer. This means that testing APIs indirectly help with testing both data and presentation layers. API testing is divided into 2 categories:Continue reading “A little bit about API Testing”

There can be situations where testers are forced to perofrm testing with no or less requirements.Here are some of the possible solutions to such cases where it is lacking or missing documentations: By talking to relevant groups of people that may have more understanding of how the system/application works or should behave Error guessing testingContinue reading “What to do when the document is lacking or missing for testing”

Risk is used to focus the effort required during testing. It is used to decide where and when to start testing and to idetnfiy areas that need more attention. This approach to testing provides proactive opportunities to reduce the levels of product risk. It involves product risk analysis to: Determine which types of testing toContinue reading “Risk-based Testing”

Test execution schedule takes into account factors such as prioritization, dependencies, confirmation tests, regression tests, and the most efficient sequence for executing the tests.Confirmation and regression tests take priority and those tests with dependencies would need to have their dependencies tested first. Then followed by test cases with higher priorities.

Managing good and healthy relationship with developers could be challenging. Some developers may become quickly defensive when testers are explaining defects/bugs. Testing under time constraint as often developers quickly become the bottleneck of the project. No or lack of/missing documentation could potentially make testing very difficult and time consuming as testers would need to scavengeContinue reading “Challenges faced by Testers”