Test estimation and proper execution plays an important role in the development cycle of any successful project. Hence, test estimation should be realistic and accurate. Below are factors affecting software test estimation and general tips to estimate accurately:
1. Think of some buffer time
2. Consider the bug cycle
3. Availability of all the resources for estimated period
4. Think the estimation based on your product version
5. Estimations can go wrong – so re-visit the estimations frequently in initial stages before you commit it
6. Think of your past experience to make judgments
The Director of National Information Technology Development Agency has said that the policy has so far remained the exclusive preserve of foreign vendors. Professor Angaye disclosed NITDA to set up centres where Nigerian local software can be tested to international standards. He also said that youths can have the opportunity of doing web analysis for job creation. The NITDA boss indicated that local software must be tested to global standards. Appropriate mechanism needed to be set up for quality assurance and global standard for testing and certification of software developed in Nigeria.
The definition of agile testing in wikipedia is that testing from the customer perspective al early as possible and testing early and often as code becomes available and stable enough from module/unit level testing. There are some challenges in agile testing testers having to face while working with agile development team.
1. Obtain number of hours commitment up front
2. Gather Requirements / Estimates up front
3. Entering the actual hours and estimated hours daily
4. Daily builds
5. Keep the daily scrum meetings short
6. Code inspections are paramount
Hence, an agile tester needs to be innovative with the tools that they have so as to meet the challenges above. Here are important keys to innovation: creative, talented, fearless, visionary, empowered, passionate, and multiple disciplines. Watts Humpry said “Innovation is the process of turning ideas into manufacturable and marketable form.”
Here is to talk about some tactics that are about how your test approach should change to address those risks, along with guidance for how and what to test specifically.
Firstly, you should shift architecture and “soft” point. Secondly is hooks and scaffolding. Then the third point is from risks to testing and the last tactic is putting it all together. Testing for cloud architectures introduces new challenges to debugging, to reproducing problems and to predicting performance.