Entries Tagged 'Test strategy' ↓
March 20th, 2014 — Test strategy, Testing Tips and resources
In the last article, we did some heavy lifting in terms of understand the healthcare domain. We are ready to put our “Tester’s hat” back on and now try to understand how to test the health care applications.
=> If you haven’t read part 1 please read it here: How to Test Health care application – introduction
We are now going to pick each application/system and come up with conditions that we are going to validate in each one of them.
This article is useful for the testers who are already in the healthcare domain or those who want to enter in this hottest career field.
Continue reading →
October 30th, 2013 — Test strategy, Testing Methodologies
There are many test case design techniques. In this article, we will learn how to use Decision Table technique effectively to write test cases for an application with complex business logic.
Decision table testing is an easy and confident approach to identify test scenarios for complex business logic.
Here is an illustration with example:
We all know that business rules and validations take up major portion of the requirements given by the customers. While observing how these requirements Continue reading →
December 7th, 2012 — Software Testing Templates, Test strategy
What is Test Strategy?
A strategy plan for defining testing approach, what you want to accomplish and how you are going to achieve it.
This document removes all uncertainty or vague requirement statements with a clear plan of approach for achieving the test objectives. Test strategy is one of the most important documents for QA team. Writing it effectively is a skill every tester should achieve in their career.
It initiates your thought process which helps to discover many missing requirements. Thinking and test planning activities help team to define testing scope and test coverage. It helps test managers to get clear state of the project at any point. The chances of missing any test activity are very low when there is a proper test strategy in place.
Test execution without any plan rarely works. I know teams who write strategy document but never refer Continue reading →
June 22nd, 2010 — Database Testing, ISTQB Certification, QA certifications, Test strategy
This article is a part of software testing questions and answers series. You can see all previous articles under this Q&A series on this page – Software Testing Questions & Answers. If you want to ask a question, just write a comment below.
What type of database (SQL) questions asked in interviews for test engineer position (not for database tester)?
This depends on many factors whether these questions are for testing positions at entry level or for experienced testing professionals. The depth of database interview questions depend on the experience of the candidate.
Continue reading →
November 26th, 2009 — Test strategy, Testing Life cycle
This is a guest article by Author “N. Sandhya Rani”.
For success of any project test estimation and proper execution is equally important as the development cycle. Sticking to the estimation is very important to build good reputation with the client.
Experience play major role in estimating “software testing efforts”. Working on varied projects helps to prepare an accurate estimation for the testing cycle. Obviously one cannot just blindly put some number of days for any testing task. Test estimation should be realistic and accurate.
Continue reading →
December 17th, 2007 — Basics of Software testing, Quality assurance, Test strategy
Are you developing any Test plan or test strategy for your project? Have you addressed all risks properly in your test plan or test strategy?
As testing is the last part of the project, it’s always under pressure and time constraint. To save time and money you should be able to prioritize your testing work. How will prioritize testing work? For this you should be able to judge more important and less important testing work. How will you decide which work is more or less important? Here comes need of risk-based testing.
What is Risk?
“Risk are future uncertain events with a probability of occurrence and a potential for loss”
Risk identification and management are the main concerns in every software project. Effective analysis of software risks will help to effective planning and assignments of work.
In this article I will cover what are the “types of risks”. In next articles I will try to focus on risk identification, risk management and mitigation.
Risks are identified, classified and managed before actual execution of program. These risks are classified in different categories.
Categories of risks:
Project schedule get slip when project tasks and schedule release risks are not addressed properly.
Schedule risks mainly affect on project and finally on company economy and may lead to project failure.
Schedules often slip due to following reasons:
- Wrong time estimation
- Resources are not tracked properly. All resources like staff, systems, skills of individuals etc.
- Failure to identify complex functionalities and time required to develop those functionalities.
- Unexpected project scope expansions.
- Wrong budget estimation.
- Cost overruns
- Project scope expansion
Risks of loss due to improper process implementation, failed system or some external events risks.
Causes of Operational risks:
- Failure to address priority conflicts
- Failure to resolve the responsibilities
- Insufficient resources
- No proper subject training
- No resource planning
- No communication in team.
Technical risks generally leads to failure of functionality and performance.
Causes of technical risks are:
- Continuous changing requirements
- No advanced technology available or the existing technology is in initial stages.
- Product is complex to implement.
- Difficult project modules integration.
These are the external risks beyond the operational limits. These are all uncertain risks are outside the control of the program.
These external events can be:
- Running out of fund.
- Market development
- Changing customer product strategy and priority
- Government rule changes.
These are all common categories in which software project risks can be classified. I will cover in detail “How to identify and manage risks” in next article.