Saturday 23 August 2014

ISO/IEC/IEEE 29119 Software Testing -The International Software Testing Standard


The new standard 29119 on software testing is finalized and is evoking responses from various tester communities. If you don't know about this standard and its controversy read on ...

The standard's description can be found at below site, as its "Standard" it will be paid, so after paying fees only you will be able to get the actual standard.

http://softwaretestingstandard.org/

It says :

========================================================
ISO/IEC/IEEE 29119 Software Testing is an internationally agreed set of standards for software testing that can be used within any software development life cycle or organisation. By implementing these standards, you will be adopting the only internationally-recognised and agreed standards for software testing, which will provide your organisation with a high-quality approach to testing that can be communicated throughout the world. There are currently five standards:

    ISO/IEC 29119-1: Concepts & Definitions (published September 2013)
    ISO/IEC 29119-2: Test Processes (published September 2013)
    ISO/IEC 29119-3: Test Documentation (published September 2013)
    ISO/IEC 29119-4: Test Techniques (at DIS stage, anticipating publiation in late 2014)
    ISO/IEC 29119-5: Keyword Driven Testing (at CD stage, anticipating publication in 2015)

Plus, based on the processes defined in ISO/IEC/IEEE 29119-2:

    ISO/IEC 33063: Process Assessment Model (at DIS stage)

The ISO/IEC/IEEE 29119 standards replace a number of existing software testing standards:

    IEEE 829 Test Documentation
    IEEE 1008 Unit Testing
    BS 7925-1 Vocabulary of Terms in Software Testing
    BS 7925-2 Software Component Testing Standard

===========================================================

People who are opposing this says:

1) Costly

2) Will be seen as mandatory skill for testers (may harm individuality and freedom)

3) May loose ability to experiment and try non-conventional ways

4) Once standard is accepted, testers can be held responsible for project failures ( non-compliance)

5) Effort will be more on documentation and process rather than testing


What you can do : Learn/Share/Write/Sign the below Petition for stopping it:

http://www.ipetitions.com/petition/stop29119


Ref:
Keep Trying, Keep Analyzing !