Welcome Kenya!

The General Assembly meeting of Lisbon 29 November approved the admission of Kenya as a new ISTQB® member.

ISTQB® welcomes T-Systems Multimedia Solutions GmbH to its Partner program!

T-Systems Multimedia Solutions GmbH has joined the program at the Platinum partnership level. 

ISTQB® General Assembly will be held in Shanghai on October 2015

The General Assembly meeting of Lisbon 29 November approved locations and dates of General Assembly meetings in 2015: The third ISTQB® General Assembly of 2015 will be held inShanghai, China on October 2015. The meeting will be preceded by working group meetings as well as an international conference.

ISTQB® General Assembly will be held in Copenhagen on 12 June 2015

The General Assembly meeting of Lisbon 29 November approved locations and dates of General Assembly meetings in 2015: The second ISTQB® General Assembly of 2015 will be held in Copenhagen, Denmark on 12 June. The meeting will be preceded by working group meetings, as well as an international conference.

ISTQB® General Assembly will be held in Tel Aviv on 26 March 2015

The General Assembly meeting held in Lisbon 29 November approved locations and dates of General Assembly meetings in 2015: the first ISTQB® General Assembly of 2015 will be held in Tel Aviv, Israel on 26 March. The meeting will be preceded by working group meetings, as well as an international conference.

More than 300,000 certifications achieved

The International Software Testing Qualifications Board (ISTQB®) is proud to announce that, as of June 2013, it has issued more than 300,000 software testing certifications world-wide. Read the Press Release for more information.

Chapter 3.1.1.2 in Agile Tester Add-On: Acceptance Test Driven Development

Acceptance Test Driven Development, like TDD, is based on the test first concept. It defines acceptance criteria and tests cases for it early in the development process, in the confirmation phase of a story development process (see paragraph 1.2.2). ATDD is a collaborative approach which allows every stakeholder to understand how the software component has to behave and what the product owner, tester, developer, and others need to do to insure this behavior. A typical process of ATDD is: 1. The whole team defines tests which give examples of intended behavior 2. Testers and/or developers create automated tests with an ATDD testing tools 3. Developers create the code of the intended behavior 4. Testers and/or developers run automated acceptance tests

ATDD creates reusable tests for regression testing. Specific tools support creation and execution of such tests, often within the context of a continuous integration process. These tools can connect to data and service layers of the application. This allows tests to be run in system level or acceptance level test environments Tests environments can be user acceptance test environments instead of development test environments. ATDD allows quick resolution of defects and validation of feature behavior before promoting code to a higher environment. It helps determine if the confirmation criteria is met for the feature. ATDD facilitates also the use of external testing teams to perform functional testing.

The text above is a sample from the upcoming Agile Tester Add-On that will be released in early 2014. Please note that Agile Tester Add-On is on alpha phase, which means that its content may change. Visit www.istqb.org to get latest information.

ISTQB® welcomes Kedros, Inc. to its Partner program!

Kedros, Inc. has joined the program at the Silver partnership level.

Merry Christmas and Happy New Year!

ISTQB® community wishes you Merry Christmas and Happy New Year!

ISTQB® welcomes SOCO Norge A/S to its Partner program!

SOCO Norge A/S has joined the program at the Gold partnership level. 

Chapter 2.2.2 in Agile Tester Add-On: 2.2.2 Managing Regression Risk with evolving test cases and test automation

Agile projects, by nature, break down features in a release into manageable pieces of work, and allocate the features to iterations. With each iteration the product starts to grow significantly; therefore the amount of testing needed also increases. Along with testing the code changes made in the current iteration, testers also need to verify no regression has been introduced on features that were developed and verified in previous iterations.

The risk of introducing regression in agile development is very high due to extensive code churn (lines of code added, modified or deleted to a file from one version to another) required when developing new features in an iterative lifecycle. The text above is a sample from the upcoming Agile Tester Add-On that will be released in early 2014. Please note that Agile Tester Add-On is on alpha phase, which means that its content may change. Visit www.istqb.org to get latest information.

ISTQB® would like to welcome Petrotechnical Data Systems B.V. to its Partner program!

Petrotechnical Data Systems B.V. has joined the program at the Gold partnership level. 

More than 300,000 certifications achieved

The International Software Testing Qualifications Board (ISTQB®) is proud to announce that, as of June 2013, it has issued more than 300,000 software testing certifications world-wide.

Read the Press Release for more information

Chapter 2.1.1 in Agile Tester Add-On: Testing and Development Activities

One of the main differences between traditional lifecycles and agile lifecycles is the idea of very short iterations, each iteration resulting in working software that delivers features of value to business stakeholders. At the beginning of the project, there is often an inception period where the high-level goals of the project are defined and testing is planned in a high-level. This is followed by a sequence of iterations, each about one to four weeks in duration. In the beginning of each iteration, the detailed planning (including testing) for the iteration is performed. A small subset of the high level goals are specified as user stories with detailed acceptance criteria (i.e., the features to be built and their test conditions, respectively), then these features are developed, integrated with the system, and tested. These iterations are highly dynamic, with development, integration, and testing activities taking place throughout each iteration, with considerable parallelism and overlap. Testing activities are done all the time (i.e. daily), not just as a final activity of the iteration.

The text above is a sample from the upcoming Agile Tester Add-On that will be released in early 2014. Please note that Agile Tester Add-On is on alpha phase, which means that its content may change. Visit www.istqb.org to get latest information.

ISTQB® welcomes Dextra Technologies to its Partner program!

Dextra Technologies has joined the program at the Silver partnership level. 

ISTQB Partner Program
Discover the program designed to support companies that invest in ISTQB® Certifications. Go to the website »»

Readmore..

ISTQB International Conference Network
Find out all the ISTQB® related conferences organized world-wide. Read more »»

Readmore..

ISTQB Award
Learn about the annual prize for contributions to the innovation, research and awareness in software quality and testing. Go to the website »»

Readmore..