Start networking and exchanging professional insights

Register now or log in to join your professional community.

Follow

Which testing methodology is best suited for a small scale start-up aiming to test Software, Firmware, Websites, Hardware and their integration?

user-image
Question added by Zubin Dutt , Senior Software Engineer - Tester , Prophecy Sensorlytics
Date Posted: 2016/10/12

Agile methodology is  best software test methodology for the startups

loraine clarito
by loraine clarito , Senior Software Quality Assurance , UL

You may consider exploring Testopia/bugill (an open source test management tool).

Nishanth mv
by Nishanth mv , service

SELENIUM AUTOMATION TEST IS SIUTABLE FOR HIGHER AND LOWER APPLICATION TESTING

Hasnain Mithani
by Hasnain Mithani , Security Guard , Merchant Dehydration

As per Requirement Analuysis

VIPINDAS V V
by VIPINDAS V V , QA/QC Engineer , Intergral Component Manufacturers

Test is the last step in traditional software development. We gather requirements, do high level design, detailed design, create code, do some unit testing, then integrate and start—finally— final test.

Since most projects run late, what do you think gets cut? Test, of course. The implication is that we deliver bug-ridden products that infuriate our customers and drive them to competitive products.

Best practice development includes code inspections. Yet inspections typically find only 70% of a system’s bugs, so a fabulous test regime is absolutely essential. Test is like a double-entry bookkeeping system that insures mistakes don’t leak into the deployed product.

 

In every other kind of engineering testing is considered fundamental. In the USA, every Federally funded bridge must undergo extensive wind tunnel tests, for instance.

Mechanical engineers subject spacecraft to an almost bizarre series of evaluations. It’s quite a sight to see a 15-foothigh prototype being nearly torn to pieces on a shaker, which vibrates at a rate that puts a thousand-Hertz tone into the air. The bridge prototype, as well as that of the shaken spacecraft, are discarded at great expense, but in both cases that cost is recognized as a key ingredient of proper engineering practices.

Yet in the software world test is the ugly stepchild. No one likes to do it. Time spent writing tests feels wasted, despite the fact that test is a critical part of all engineering disciplines. Many segments of the embedded systems design community have thankfully embraced test as a core part of their processes, and advocate creating tests synchronously with writing the code, realizing that leaving such a critical step till the end of the project is folly.

More Questions Like This