Posts Tagged ‘QA Efforts’
Although proper testing requires substantial amount of time and effort in planning and execution, there are situations when time is limited and full-fledged testing runs against the time limitation. How can testers handle such situations?
When facing a limited time frame available for testing, we need to effectively use the available time and resources. Starting the testing of the project with an assumption that “We can’t test everything, no matter what” will really help in prioritizing tasks. Do a risk analysis to identify functionalities with the highest risks and functionalities that will be used by the maximum number of users. Do an analysis about what to test first and in which sequence.
Also, preparing a checklist that focuses on major key areas covered during testing will help testers, by ensuring that they are not missed out in the tight scheduled testing. The checklist should cover
Majority of the testers will focus more on testing the product against client requirements – which we mention as Functional Testing and pay less attention to non-functional testing. Non-functional requirements often play a significant role in differentiating between a product that is well received by customers vs one that may not do well in the market place. Some of the key non-functional requirements include Usability, Performance, Security, and Interoperability & Compatibility. To be more precise, Functional requirements define what a system will do while Non-functional requirements describe how the system will do it. Non-functional requirements characterize the behavior that is required in functional requirements
There are some situations which really makes the QA users and project managers to think about importance of non-functional testing for their products. A few of them would be
I have earlier written in Part I about the challenges of a testing organization. We also touched upon shortly about the solution, which is a Testing Centre of Excellence (TCoE). In this post, let us see in detail what exactly a Testing Centre of Excellence is.
In a traditional model of testing, members of separate project teams do the verification and validation in the software development lifecycle. These teams need to be trained for each project and is not an efficient process. Additionally, they cannot ensure consistent quality across a business unit as they are focused on specific projects that have varying levels of budget allocation.
Assume that there are 6 projects that are carried out in a business unit; each project will have phases like requirements, design, development, testing, deployment and support. In a TCoE, testing as a function is kept as a shared service across all the 6 projects that provide unbiased verification and validation.
I am planning to cover this topic in two parts:
Part I will deal with the challenges of a testing organization and the solution for the challenges.
Part II will specifically talk about the solution in detail and how to implement the solution.
The challenges of the testing organization can be categorized as follows:
Business Analyst Challenges
- Product does not meet user requirements. Business requirements are not properly transformed into functionality
- Time spent to support different teams for requirements clarifications is too high
- Customer is facing lots of issues after ‘Go Live’
- Cost and effort spent are increasing exponentially
- Availability of software, to market on time are always a question mark
- Requirements keep on changing and we don’t get clarification on time