In Chapter 1.2.3 in Agile Tester Add-On: The Role of an Agile Tester in Retrospectives

Testers should play an important role in the retrospective, since they can bring in a relevant “second opinion”, an outside point of view. As an important player of the team, the agile tester is also asked to provide feedback and input for non-testing- related topics. On the other hand, the other team members are also allowed and asked to leave their opinion about testing topics. The tester should participate actively and raise test-related topics as well. Since the tester is part of the team and testing is done with every sprint, it is very important that testing activities are also covered and critically analyzed within the retrospective. Based on this analysis, the tester might decide to adapt test processes to improve its own test effectiveness, test productivity, test case quality, and team satisfaction. Also the testability of the applications, user stories, features or system interfaces are critical to evaluate. Possible improvements to suggest can be identified also on a root-cause-analysis done on occurred defects (Why did we have this defect? What can be done to prevent such a defect in the future? Why did the test team identify this defects and not the automated unit test?).

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.

Chapter 1.2.2 in Agile Tester Add-On: Collaborative User Story Creation

Typically the tester’s unique perspective will improve the user story for missing details or non-functional requirements. Good approach for testers is to ask open questions from product owner concerning the user story or to ask product owner how he would test the user story as a tester. It will also help product owner to see what level of information is required by the team to produce working software per iteration. For example, a story can describe a feature that will be coded by a developer of the Agile team. But this feature will interact with another application, or add information in a database used by another application. In this case, it will be useful for the developer, the tester and business stakeholders to have user stories that describe how the feature will work internally and with other applications via the database. A coded function will extract data from a database which will be used with a business intelligence tool. A user story may state, “As an analyst I want to view data in a statistics tool after extraction so that I can analyze it”. The developer will write and test the “extract” function per the functional user story, and an interoperability user story, or a sub-task of the user story will explain how data will be used. Each story will specify acceptance criteria for these functional and non-functional characteristics. These criteria provide the developer and tester with an extended vision of the feature that the product owner and business or operation stakeholders will validate.

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 in its alpha phase, which means that its content may change. Visit www.istqb.org to get latest information.

ISTQB® welcomes SOFTWARE ENTERPRISE SERVICES S.A.C to its Partner program!

SOFTWARE ENTERPRISE SERVICES S.A.C has joined the program at the Silver partnership level. 

ISTQB® welcomes TestDevLab Ltd. to its Partner program!

TestDevLab Ltd. has joined the program at the Gold partnership level.

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 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..