Ivesia Solutions Inc

The moment we mention software quality, the first thing that comes to our mind is bug-free software. Is bug-free software the only thing about software quality?Absolutely not!

We can define software quality thus, it is a part of each phase of the development life cycle including testing and encompasses a whole load of factors and not just bug-free and aesthetic software. These factors that are a combination of tangible and intangible sum of quality attributes like functionality, reliability, usability, efficiency, maintainability and scalability forms an important part of the software.

A bug free, aesthetically appealing product that fails to solve business problems … Continue Reading

Pair Testing is one of the interesting testing methodologies where a pair – developer and Tester, or 2 testers, or sometimes tester and business user will test the application. This kind of testing approach is followed in situations when the requirement and specification is not very clear or the team is new and need to learn the application in a short spam

Pair Testing gains the advantage of analysing the root cause of major bugs easily and since the tester is aware of bug root cause, he/she may start with exact test scenarios to capture bugs and can easily test the … Continue Reading

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 … Continue Reading

It is a quite common comment received from a developer, that the Bug report is not clear. The steps to reproduce are Vague, captured screenshot is not effective, and many more are usual complaints which tester can hear in his career. Hence, reporting a bug efficiently and effectively is as important as identifying bugs. Reporting a good bug is not hard, but many times we do it in a hurry and without putting our full attention into it and hence when a bug is not reported properly it may end up in

1. Wasting our time to report bug incorrectly and additional … Continue Reading
   

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 … Continue Reading

Whenever a software organization delivers a new project or customizes an enhancement feature for an existing product, it always strives for client satisfaction. While various testing approaches and methodologies are followed within organizations to increase the quality of output, the most important testing for client satisfaction is User Acceptance Testing. During this testing, actual business users will get to test the enhanced product. UAT (User Acceptance Testing) is the last major test before delivery. If UAT goes badly, it is fair to say that much of the good work prior to UAT is wasted.

What is UAT (User Acceptance Testing)?

The explanation of UAT … Continue Reading

One of the greatest challenges that a tester comes across in his testing is dealing with intermittent bugs. These are mysterious, undesirable bugs  that have been observed at least once, but cannot be easily re-created. Or in simple terms, they are also called as ‘non-reproducible’ bugs. Most of the testers would have come across situations quite often in their career where some bugs cannot be reproduced again. Usually, the common answers offered by testers for this kind of bugs are

• This bug is not producible always. We have captured the log.
• It doesn’t occur if we re-start the application
• It will take significant … Continue Reading
  

For a tester, reporting bugs and keeping track of them is as important as finding bugs.  And hence Bug Reporting gains the highest priority in the QA Process. There are so many reasons and advantages for using a bug tracking tool such as increased productivity, having everyone in the project be aware of bug status and progression, formalized way of reporting bugs and so on. Though some individual organizations develop, use and maintain their own bug tracking tool, there are numerous open source bug tracking applications available in the market to use. It is vital for the QA management to … Continue Reading

Defect free or bug free software is in the wish list of many software vendors for ages and it hasn’t materialized and people are still looking for the Holy Grail. No piece of software can be bug free, however we can ensure that it works well in a controlled environment.

Defects are introduced in the software at all phases starting from requirements to analysis to design to development to verification to implementation to maintenance. In addition, 50% of the bugs are introduced when programmers try to fix a known bug. Essentially, any activity that is performed by a programmer or a … Continue Reading

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 … Continue Reading