ISTQB® Effectiveness Survey

According to the ISTQB® Effectiveness survey approximately 70% of Test Managers consider it important to obtain Advanced Level certifications, and this opinion is shared by 63% of Test Engineers. See the full report.

In Chapter 3.1.4 in Agile Tester Extension: The Role of a Tester Teamwork

Teamwork is a fundamental principle in Agile development. Agile emphasizes the whole-team approach consisting of developers, testers, and business representatives working together. The following are team organizational and behavioral best practices in Scrum teams:de in the team, how to organize themselves and how to divide their work. There could be teams with only developers (also doing all their needed testing), only one tester, or two or more dedicated testers. It is an advantage having two or more testers as they can work more efficiently together in so called “pair testing”.

  • Cross-functional: The team works efficiently together on the test strategy, test planning, test specification, test execution, test evaluation, and test results reporting.
  • Self-organizing: The team may consist only of programmers, but, as noted in Section 2.1.5, ideally there would be one, two, or more testers. It is an advantage to have two or more testers, as they can do pair testing.
  • Collocated: Testers sit together with the programmers and the product owner.
  • Collaborative: Testers collaborate with their team members, other teams, the stakeholders, the product owner, and the scrum master.
  • Empowered: Technical decisions regarding design and testing are made by the team as a whole (programmers, testers, and scrum master), in collaboration with the product owner and other teams if needed.
  • Committed: The tester is committed to question and evaluate the product's behavior and characteristics, with respect to the expectations and needs of the customers and users.
  • Transparent: Programming and testing progress is visible on the Agile task board (see Section 2.2.1).
  • Credible: The tester must ensure the credibility of the strategy for testing, its implementation, and execution, otherwise the stakeholders will not trust the test results. This is often done by providing information to the stakeholders about the testing process.
  • Open to feedback: Feedback is an important aspect of being successful in any project, especially in Agile projects. Retrospectives allow teams to learn from successes and from failures.
  • Resilient: Testing must be able to respond to change, like all other activities in Agile projects.

    These best practices maximize the likelihood of successful testing in Scrum projects.

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

In Chapter 3.1.2 in Agile Tester Extension: Recall the concepts of the Test Pyramid

A software system can and has to be tested on different levels of abstraction. Typical such levels are (see [ISTQB Foundation Level Syllabus, 2011, Chapter 2.2]): Component Testing, Integration Testing and System Testing. These levels of abstraction exist for every product/system, regardless whether the system was or is build following a traditional development model or an agile development approach. As a result a project team creates and maintains test cases on each of these levels. The interfaces to be called or stimulated by a specific test case can look quite different depending on the test level of the specific test case. So if a test case is automated the test tool in use must be appropriate for the level specific test interface. Usually component and integration level tests are automated using so called 'Unit Testing Frameworks' (see [Meszaros 07]). On system level functional tests are often automated using so called 'GUI-Testing Tools' to simulate interactions of a system end user with the system via the systems Graphical User Interface (GUI). But depending on the systems technical architecture and the test type (e.g. performance test) it could be necessary or possible to execute a system level test case via the systems API (e.g. a service API) rather than via its GUI and thus to automate such test cases using a specialized testing tool (e.g. for performance testing) or even to use a Unit Testing Framework (interfacing the system level API).

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 Nokia Solutions and Networks Oy to its Partner program!

Nokia Solutions and Networks Oy has joined the program at the Platinum partnership level. 

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

ISTQB Christmas

ISTQB® welcomes Q-leap S.A. to its Partner program!

Q-leap S.A. has joined the program at the Silver partnership level. 

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.

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