Ivesia Solutions Inc

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

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

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

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

Management Challenges

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

Software companies need to take concepts to products quickly so that they can reach the market faster. However, in this process, sometimes they end up building a monster application, which upon maturity, companies have to spend tons of time and money in scaling.

Let me explain this in detail. In your development efforts, doing it right the first time is always costly and time consuming. A workaround will take less time and will probably save a whole load of money from the budget. The general attitude is that we will fix it as we go along when we have the resources. … Continue Reading