news from ISEB

Some news. ISEB are now able to offer the following qualifications:

Intermediate Certificate in Software Testing

This qualification bridges the gap between foundation level and practitioner level, and addresses the need for the candidate to adopt a different approach in thinking than that required at foundation level.

Practitioner Certificate in Test Management

Enables testing practitioners to gain professional recognition for advanced level skills in the managerial aspects of testing.

Practitioner Certificate in Test Analysis

This qualification enables testing practitioners to gain professional recognition for advanced level skills in the more technical, analytical aspects of testing.

These were created because of the gap between previous Foundation and Practitioner Certificates. Also testers tend to specialise in either the management of testing or in test analysis but seldom both disciplines, many candidates who had taken the exam recommended in their feedback that it would be beneficial to develop separate exams for each.

The new ISTQB (International software Testing Qualifications Board) syllabus is now used for all ISEB Foundation Certificate in Software Testing examinations. The Foundation Certificate in Software Testing now has dual accreditation with the ISTQB (International Software Testing Qualifications Board) and successful candidates will receive certification with both ISEB and ISTQB recognition at Foundation level. The exams are available to be taken at Authorized Prometric Test Centers (APTCs).

  • ISEB candidates can obtain ISEB qualifications throughout the year rather than at pre-set exam dates
  • Examinations can be booked with less than two days notice
  • Results are immediately available
  • Computer based exams eliminate the need for examination papers and answer sheets and gives an extra level

Comments

Post a Comment

Popular posts from this blog

Retrofitting testing - what is it?

It is nice to meet new terms and keywords relating testing. This morning I got a question how I am planning to do 'regression as part of Code Retrofitting testing'.   Have never heard of retrofitting testing before, so did some googling. The best explanation I found was on blog  http://blog.intrepidtesting.com/retrofit-vs-retest-vs-regression-testing/    article " Retrofit vs Retest vs Regression Testing " : Retrofit testing  is carried to to test that a change in functionality is correctly implemented for existing entities. Retrofit testing is more commonly carried out when you have an incremental project, or change requests. If the time available to test is tight, retesting and retrofit testing usually takes a higher priority over regression testing Colleague's comment while trying to help me: " if I googled it correctly then they expect you to perform regression for legacy system where your changes were introduced. In this way I would ...
Read more

tester's day!

Happy testers day! Top 24 replies by programmers when their programs don't work: 24. "It works fine on MY computer" 23. "Who did you login as ?" 22. "It's a feature" 21. "It's WAD (Working As Designed)" 20. "That's weird..." 19. "It's never done that before." 18. "It worked yesterday." 17. "How is that possible?" 16. "It must be a hardware problem." 15. "What did you type in wrong to get it to crash?" 14. "There is something funky in your data." 13. "I haven't touched that module in weeks!" 12. "You must have the wrong version." 11. "It's just some unlucky coincidence." 10. "I can't test everything!" 9. "THIS can't be the source of THAT." 8. "It works, but it's not been tested." 7. "Somebody must have changed my code." 6. "Did you check for a virus on your system?...
Read more