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.

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