In Chapter 3.1.1 in Agile Tester Extension: Test Driven Development

Test Driven Development (TDD) is more a development technique than a test technique. A developer may perform low level testing using the Test Driven Development, while a tester or product owner performs high level testing using Acceptance Test Driven Development (ATDD). Behavior Driven Development (BDD) can include both low level and high level tests.

Test Driven Development

Test driven development is a technique used to develop code guided by automated test cases. It is also known as test first programming, since test cases are written before the code. Test driven development includes:

  • Add a test that captures the programmer’s concept of the desired functioning of a small piece of code
  • Running the test, which should fail, since the code doesn’t exist
  • Writing the code and running the test in a tight loop until the test passes
  • Refactoring the code after the test is passed
  • Repeating this process for the next small piece of code, running the previous tests as well as the added tests

The test cases written are primarily unit level and typically code-focused (white-box), though tests may also be written at the integration or system levels. Test driven development was popularized by Extreme Programming [Beck02] but is used in other agile methodologies and sometimes in sequential lifecycles. This development approach allows fixing coding defects as soon they are introduced.

Test driven development reduces the introduction of defects by helping the developer focus on the clearly defined expected results. The tests serve as a form of executed design specification for future maintenance efforts. The tests are automated and are used in continuous integration.

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

ISTQB® welcomes Sogeti Belgium NV to its Partner program!

Sogeti Belgium NV has joined the program at the Gold partnership level. 

ISTQB® welcomes Make it Work (Tecomoni Srl) to its Partner program!

Make it Work (Tecomoni Srl) has joined the program at the Silver partnership level.

ISTQB® to welcomes Make it Work (Tecomoni Srl) to its Partner program!

Make it Work (Tecomoni Srl) has joined the program at the Silver partnership level.

Expert Level Test Manager exams will be offered during ASTQB Conference 2014!

In addition to Foundation and Advanced Level exams, Expert Level Test Manager exams will be offered during ASTQB Conference 2014!

These Expert Level exams will be held for the first time ever. See more information at the ASTQB Software Testing Conference page.

ISTQB® welcomes MTA S.p.A. to its Partner program!

MTA S.p.A. has joined the program at the Silver partnership level.

The First Expert Level course ever has started in Netherlands!

The first Expert Level course "Improving the Testing Process - Module Assessing Test Processes" has started in Netherlands. See more information in www.bntqb.org

ISTQB® welcomes Telerik AD to its Partner program!

Telerik AD has joined the program at the Gold partnership level.

In Chapter 3.2.2 in Agile Tester Extension: Estimating Testing Effort Based on Content and Risk

The agile project test strategy or test approach (the distribution of the test effort and coverage over the items to be tested) is defined during the planning event and included in the backlog. For example, during the planning stage, the agile team estimates, with the aid of planning poker, the size (often estimated in story points) for each story of a product backlog. Planning poker is the ideal way to formulate relative estimation size; i.e., where the estimations are related to one another. A reliable estimation is made by the whole team. By means of cards, everyone allocates story points to the estimated size of a backlog item. Aspects such as effort, complexity and the thoroughness of testing (in relation to the product risk) play a role in the estimation. Therefore, it is advisable to include the risk classification of a backlog item - particularly in the case of user stories - in addition to the priority specified by the product owner, before the planning poker is initiated. Differences in estimates are discussed, after which the card-playing is repeated until consensus arises. The discussion that produces this means of evaluation ensures that nothing is forgotten and that everyone is involved. This ensures a reliable estimation of the work — across the various disciplines — which is needed to complete a product item and to boost collective knowledge of what has to be done.

See also Kelly Waters article about this topic:

http://www.allaboutagile.com/estimating-in-agile-development/

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

ISTQB® welcomes Systek AS to its Partner program!

Systek AS has joined the program at the Silver partnership level.

In Chapter 1.2.4 in Agile Tester extension: Benefits of Continuous Integration

Each change on the code base or configuration is verified by an automated build and test, allowing teams to detect problems early

  • The working code is committed and tested frequently, the team always knows if the code is working or not
  • By integrating regularly, errors are detected quickly, and can be located and analyzed more easily
  • Early identification of conflicting changes
  • Provides confidence that the next sprint is based on a solid foundation
  • Making progress is visible and encourages developers and testers
  • No long integration efforts at the end of a project
  • When unit tests fail or a bug emerges, developers might revert the codebase to a bug-free state, without wasting time for debugging and defect clearing
  • Constant availability of a deployable software at any time and at any place for testing, demo or education purposes
  • Reduces repetitive manual test activities
  • Impact of decisions made to improve quality and tests are shown immediately

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

Chapter 1.2.4 in Agile Tester Add-On: Continuous Integration

An important concept of any agile software development is getting reliable, working and integrated software at the end of every sprint or iteration. Continuous integration is a software development practice addressing this challenge by merging all changes made to the software and integrate all changed components regularly, at least once a day. Goal is to wrap compilation, build, deployment and testing into a single, automated and regularly repeatable process. Continuous integration can also be seen as a process in which developers integrate their work constantly, build constantly, and test constantly so errors in code can be detected more quickly.

A full continuous integration process consists of the following activities:

  • Coding: write and debug code
  • Checking-In: transfer the code in a centralized source code repository
  • Static testing: execute and report automated static testing
  • Building: a build tool automatically builds the code
  • Unit testing: execute, measure coverage and report automated unit testing
  • Deploying: automatically deploy the build
  • Integration Testing: execute and report automated integration testing
  • Reporting (dashboard): make the status of all previous bullets/activities visible automatically

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.

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

Chapter 1.1.2 in Agile Tester Add-On: Using the Whole Team Approach

In agile projects, quality is the responsibility of the Whole Team: they 'own' the product and have responsibility for its successful delivery. An agile testing team therefore, will have responsibility not just for integration and system test, but will also work closely with both developers and the business representatives to ensure quality across all test levels. This includes supporting and collaborating with business representatives to help them create suitable acceptance tests. Any consultations or meetings in which product features are presented, analyzed or estimated will involve the Whole Team. The concept of involving testers, developers and business representatives in all feature discussions has been called the 'Power of Three' [Crispin and Gregory, 2009].

The text above is a sample from the upcoming Agile Tester Add-On that will be released in early 2014. Visit www.istqb.org to get latest information.

2013 Award Winner is Harry Sneed!

ISTQB® is proud to announce that the Winner of 2013 "ISTQB® International Software Testing Excellence Award" is Harry Sneed for his outstanding contribution to the software quality and software testing.

Read the Press Release or visit awards.istqb.org for more information

Chapter 1.1.1 in Agile Tester Add-On: Agile Software Development and the Agile Manifesto

In 2001 a group of individuals, representing the most widely used lightweight software development methodologies, agreed a common set of values and principles which became known as The Manifesto for Agile Software Development or Agile Manifesto. The Manifesto was created as an alternative to traditional “waterfall” style development approaches which the Manifesto creators perceived as document driven and overly bureaucratic. The Agile Manifesto states four key values: 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan. 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 Testing IT Consulting to its Partner program!

Testing IT Consulting has joined the program at the Gold partnership level.

Introduction to new Foundation Level Agile Tester Add-on

The Foundation Level Agile Tester Certification is aimed to bring knowledge to the testers and test leaders who are working within Agile environments or that are (or their company is) planning to start implementing Agile in the near future. The certification is providing an advantage for those who would like to know the required activities, roles, methods, methodologies of Agile environment specific for their role. This includes people in roles such as Testers, Test Analysts, Test Engineers, Test Consultants, Test Managers, User Acceptance Testers and Software Developers.

Foundation Level Agile Tester Add-on qualification is also appropriate for anyone who wants a deeper understanding of software testing in the Agile world, such as Project Managers, Quality Managers, Software Development Managers, Business Analysts, IT Directors and Management Consultants.

Agile Tester Add-On will be released in early 2014. Visit www.istqb.org to get latest information.

ISTQB® welcomes XDIN to its Partner program!

 XDIN AB has joined the program at the Platinum partnership level.

ALTEN becomes first ISTQB® Global Partner

ISTQB® is pleased to announce that ALTEN has become the first organisation to achieve the Global Partner status with ISTQB®.

Read the Press Release or visit www.istqb.org/partner for more details about the Partner Program

ISTQB® welcomes Maint Cia Ltda. to its Partner program!

Maint Cia Ltda. has joined the program at the Silver partnership level.  

Develop an ISTQB® recognized mobile app!

ISTQB® created the “ISTQB® Recognized App” concept in order to promote mobile device applications based on ISTQB® referenced information. Anyone can submit a mobile device app for consideration as an ISTQB® Recognized App and, if successful, will be entitled to use the “ISTQB® Recognized App” logo. To find out more, read http://www.istqb.org/about-istqb/istqb-recognized-mobile-app.html

ISTQB® welcomes Steria Mummert Consulting AG to its Partner program!

Steria Mummert Consulting AG has joined the program at the Platinum partnership level. Visit the Partner program page for more information.

Global pass-rate of ISTQB® exams

ISTQB® exams are designed and monitored according to strict, internationally consistent, criteria. They are based on a precisely defined number of questions, varying depending on certification level, and a distribution of questions across the syllabi, according to topics and K-Levels. The global pass-rate of ISTQB® exams (world-wide average since inception) as of March 2013 is reported here http://www.istqb.org/exams-root.html

ISTQB® welcomes System Verification Sweden AB to its Partner Program!

System Verification Sweden AB has joined the program at the Platinum partnership level.

Visit the Partner Program page for more information.

Winner of 2013 "ISTQB® International Software Testing Excellence Award" to be announced in Portugal in November

Each year the ISTQB® awards a prize to somebody who is recognised as having made an outstanding contribution to the field of software quality through professional practice, innovation, or research. The next winner will be announced in Lisbon, Portugal, in November. For more information please visit http://awards.istqb.org/.

ISTQB® would like to welcome SQS AG to its Partner program!

SQS AG has joined the program at the Platinum partnership level. Visit the Partner program page for more information.

New ISTQB® Add-on under development: Agile Testing

To meet the demand for testing certification within specific domains, ISTQB® has introduced the concept of an “add-on”. The first of these will be focused on Agile Testing and is planned for release in early 2014.

ISTQB® welcomes Sogeti Deutschland GmbH to its Partner program!

Sogeti Deutschland GmbH has joined the program at the Platinum partnership level. For more information visit the Partner Program page.

More Articles ...

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