MENU

Blog

Xento is a product based organisation with more than 600 IT Professionals including 350+ PHP Professionals working with a healthy dose of creativity and innovation. We promote an open atmosphere, where team members freely voice new ideas and are involved in all phases of our growth. At Xento, working is not just work; it's fun. Nurturing individual talent, fostering team work and recognition are the key elements of the Xento Culture.

Test Then Code

Posted by: Sanjay Garg | Category: Newsletter, Oct-2014, Software Quality

We all are doing testing in our day to day life. You must have shopped with a female, how many questions they ask before buy? Even too much bargain. I know, sometimes very frustrated, but if you see at the different side of the coin, they end up with very good deals.
In this article, I am focusing on this kind of approach for doing software testing.

“Test then Code” is the phrase which I came across while reading ISTQB advanced level syllabus. It’s nothing but the requirement based testing strategy.

For any application, most important part is user requirements. If requirements are captured correctly, then we can reduce significant number of defects in initial phase itself.
In development of any project, our first focus should be collecting the requirements. Once requirements are captured and signed off, then only we should focus on development.

In testing, we all have read that finding a defect at early stage is much cheaper than finding the defect at later stage. But, still we skip the QA (Quality Analysis) part. If our requirements are not correct how we can build the right product or deliver the quality product.

Tester should behave like a kid. Have you seen a kid asking questions? They ask same questions multiple times showing you a different view. If you give different answer then they catch you and ask again about the previous answer.

My point here is, tester should test the requirements with different perspective. They should analyze the requirements for positive and negative scenarios. In requirement phase, Tester should play a role of BA. This can be happen only when Tester is part of requirements gathering and analysis.

It means, industry needs to increase the testing budget. In most of the projects, testing budget is very less compared to the overall project budget. If industry wants to deliver a product of high quality then they need to increase the budget of testing.

Testing is more approach oriented. Irrespective of the development life cycle industry is using, tester should be a part of each and every phase of SDLC. Tester should be involved in project as early as possible.

Testing is not a less-skilled job. It requires different mind set and different thinking capability. Tester should play different roles. He/She needs play a role of BA, QA, QC, Customer, End User, Stakeholder and Employee.

“Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous.” – James Bach

Happy Testing and keep learning.

Sanjay Garg