If you would like to provide us with feedback on how ISTQB® certification has worked for you or your staff, please complete our 10-minute survey (around 20 questions) which will be open until 30 September 2013.
Two versions are available:
Please see more information and answer the survey here. Your opinion is important for us.
Test tools can greatly improve the efficiency and accuracy of the test effort, but only if the proper tools are implemented in the proper way. Tell us about your experiences and leave your comment under this topic.
The ISTQB® International Software Testing Excellence Award is an annual prize, given for outstanding contribution to the preservation, innovation or research in the field of software quality. Everyone can submit a proposal for a potential winner of the ISTQB® International Software Testing Excellence Award, nominating private individuals, institutions, companies or organizations. Submit your nomination here!
Much of a Test Analyst’s job requires the effective use of tools. Knowing which tools to use, and when, can increase the Test Analyst’s efficiency and can help to provide better testing coverage in the time allowed. Learn more and download the Syllabus here
ISTQB®, the International Software Testing Qualifications Board, has chosen Mr. Chris Carter, founder of Planit Australia and a respected figure in software testing internationally, to be its new elected president for 2013-2014.
Representatives from over 40 national testing boards cooperate in ISTQB® to set the global standard for the training and certification of software testers worldwide. More than 280,000 professional have already been certified according to the ISTQB® Certified Tester Foundation and Advanced Level standard.
The general assembly meeting of ISTQB® was held in Toronto, Canada on Friday 12th of April 2013. During this meeting elections for the new Executive Board for ISTQB® were conducted.
As a Board Member of the ISTQB® and ANZTB, Chris Carter has been a major driver in advancing the Australian and New Zealand testing. More in ISTQB® elections: The former President Mr. Yaron Tzubery from the Israeli Testing Board was elected as Vice President. Mitko Mitev from the South East European Testing Board (SEETB) was re-elected as Treasurer and Eric RIOU du COSQUER, from the French Testing Board was re-elected as Secretary.
The ISTQB® General Assembly thanks Mr. Yaron Tsubery for his work and wishes the new ISTQB® President Chris Carter and other Executives good luck in the next two years of their terms.
More information about ISTQB® working rules and management structure can be found here
A successful review process requires planning, participation and follow-up. Test Analysts must be active participants in the review process, providing their unique views. They should have formal review training to better understand their respective roles in any review process. Learn more and download the Syllabus here
ISTQB® formalized partnerships through its partner programs with more than 20 companies in various countries. Partners range from small entities that got the Silver Level to bigger companies that achieved the Gold or Platinum Level. See more details here
ISTQB® in co-operation with ASTQB makes available the E-book version of the ISTQB® Syllabi, in EPub and Kindle (just Foundation Level) format. You can download these e-books here
Test Managers communicate with a wide audience, including users, project team members,management, external testing groups and customers. Communication must be effective for the target audience. Tell us about your experiences and leave your comment under this topic.
The Test Analyst should concentrate on the software quality characteristics of functionality and usability. Accessibility testing should also be conducted by the Test Analyst. Although it is not listed as a sub-characteristic, accessibility is often considered to be part of usability testing. Testing for the other quality characteristics is usually considered to be the responsibility of the Technical Test Analyst.
While this allocation of work may vary in different organizations, it is the one that is followed in these ISTQB® syllabi. Learn more and download the Syllabus here
The test design techniques considered in this chapter are divided into the following categories:
These techniques are complementary and may be used as appropriate for any given test activity, regardless of which level of testing is being performed. Learn more and download the Syllabus here
All these events, held on a yearly basis, have to:
Recognition is based on the certain criteria.If you are a conference organizer and you would like to join the ISTQB® Conference Network, contact us at firstname.lastname@example.org. See more information on our web site
Product risks, defects, tests, and coverage can be and often are measured and reported in specific ways during the project or operation by the Test Analyst. Confidence, though measurable through surveys, is usually reported subjectively. Gathering the information needed to support these metrics is part of the Test Analyst’s daily work. Learn more and download the Syllabus here
The long-term lifecycle approach to testing should be considered and defined as part of the testing strategy. The moment of involvement for the Test Analyst is different for the various lifecycles and the amount of involvement, time required, information available and expectations can be quite varied as well. Because the testing processes do not occur in isolation, the Test Analyst must be aware of the points where information may be supplied to the other related organizational areas. Learn more and download the Syllabus here
Successful Test Managers recruit, hire and maintain teams with the proper mix of skills. Skills requirements may change over time, so in addition to hiring the right people in the first place, providing adequate training and growth opportunities are important in order to retain the test team and maintain it at a level of peak performance. In addition to the skills of the team, the Test Manager must also maintain a set of skills that will allow effective functioning in a high pressure, fast-paced environment.
Learn more and download the Syllabus here
There are a variety of different issues that a Test Manager must consider when selecting test tools. Test tools are a long-term investment, likely extending over many iterations of a single project, and/or applicable to many projects. A Test Manager must consider a prospective tool from several different viewpoints.
Learn more and download the Syllabus here
Boost your business and take advantage of the ISTQB® Partner Program web site. You can use it in many ways:
ISTQB® created the "ISTQB® Recognized Mobile App" in order to promote those applications that are based on ISTQB® referenced information. Any person or entity can apply to have an ISTQB® recognized App and the app will be reviewed by the ISTQB® that will check the certain criteria. Read more about the criteria and other details here.
ISTQB® operates through a General Assembly, an Executive Committee and a number of Working Groups (WGs). ISTQB® constitution defines that the General Assembly (GA) has the power to approve the objectives and activities of the association; as such, it is the most important body of ISTQB®. The GA ensuring a democratic and transparent approach that is a hallmark of the ISTQB®. Next ISTQB® GA meetings will respect the "rotation" across the various continents and are planned as follows:
Testing often accounts for a major part of the total project costs. However, only limited attention is given to the test process in the various software process improvement models. Process improvements are relevant to the software development process as well as to the testing process. Learning from one's own mistakes makes it possible to improve the process that organizations are using to develop and test software. Learn more and download the Syllabus here.
When a defect is detected (as part of static testing), or a failure is observed (as part of dynamic testing), data should be gathered by the person(s) involved and included in the defect report. This information should suffice for three purposes: 1. Management of the report through the defect lifecycle 2. Assessment of project status, especially in terms of product quality, and test progress 3. Assessment of process capability (as discussed in Section 4.4) Learn more and download the Syllabus here.
An organization's defect management process and the tool used to manage this work are of critical importance not only to the test team but to all teams involved in the development of software. Defects may be introduced at any point in the software development lifecycle and in any software-related work product. Therefore, each phase of the software development lifecycle should include activities to detect and remove potential defects. Learn more and download the Syllabus here.
ISTQB® awarded Dorothy for her notable contributions to the improvement of software quality and software testing. The ceremony was held on December 2012 in London with the presence of Marketing Working Group Chair, ISTQB® President and UKTB President. See the picture below and read more about the Award here.