ISTQB® community wishes you Merry Christmas and Happy New Year!
ISTQB® community wishes you Merry Christmas and Happy New Year!
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.
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
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.
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.
Systems Development Consultants SDConsult Co. Llt. has joined the program at the Silver partnership level.
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.
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® 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® 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
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/.
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.
The ISTQB® General Assembly on 23 August at Helsinki voted and approved the exclusion of Saudi Arabian Board. See more information about member boards.
Join us for the Testing Portugal conference, now into its fourth year, and attracting testing professionals from all over the region. Organised by the Portuguese Software Testing and Qualifications Board, this annual event is presented in both Portuguese and English, and is free to attend. For more details visit the Conference Page.
This short presentation is available on our website and answers questions including: What is the ISTQB®? How many questions are there in an Advanced Test Manager exam? What is an "add-on"? To obtain ISTQB® in a Nutshell, please visit ISTQB® in a Nutshell webpage.