Request Free Consultation

Experimentus

  • About
    • What Makes Us Different
    • Board Of Directors
    • Partners
    • Industries
  • Customer Journey
    • Assess
    • Visualise
    • Transform
    • Manage
    • Train
  • Products and Services
    • Software Testing Services
      • Test Process Improvement
      • Software Quality Health Checks
      • Software Quality Assurance Services
      • Test Management
      • Performance Testing Services
      • Sustainable Software Testing
    • Test Environment Management
      • What is TEM?
      • TEM Challenges
      • Intelligent Test Environment Management
    • iTM – intelligent Test Method
    • TMMi – Test Maturity Model integration
  • Licencing
  • Training
    • Our Online Courses
      • Your Profile
    • TMMi Professional eLearning Course
    • TMMi Professional Public/In-house Course
    • TMMi Assessor/Lead Assessor Course
  • Resources
    • News
    • Blog
    • Case Studies
    • Web Presentations
    • Testimonials
  • Contact
You are here: Home / Agile Testing / Black-box test design in Agile

26 April 2022 by Tim Moore Leave a Comment

Black-box test design in Agile

In the final post of a series of blogs on Testing in Agile, featuring excerpts from our ISTQB Foundation Agile Tester course, we discuss how Black-box test techniques apply in an Agile context where people often assume they only apply to sequential methodologies.

In Agile projects tests are often created by testers in parallel with the developers’ programming activities. The developers create their code based on user stories and acceptance criteria, and the testers should be creating their tests using the same test basis.  Some tests, however (such as exploratory tests and some other experience-based tests) are created later, at the same time as test execution.

Black-box test techniques

Even in Agile testing, testers can (and absolutely should) still apply the black box test design techniques found in traditional methodology testing where it is appropriate to do so. The techniques that are covered in the ISTQB foundation course on software testing, such as equivalence partitioning, decision tables, and state transition testing are some that can be used to design test cases in an agile project. A specific example would be boundary value analysis, which could be used to design a test for the selection of test values in an application where a customer is limited in the number of items they may select for purchase.

Black-box test design techniques can also be used to create tests for non-functional quality characteristics. For example, a user story could contain performance or reliability requirements, such as the time for a given execution cannot exceed a specified value, or a number of operations may only fail fewer than a certain number of times.

Retaining these core test design techniques, often learnt right at the start of your testing career, can ensure that the depth an breadth of testing completed on a deliverable is maintained regardless of the methodology in use.

For more information on our self-paced learning, check out our available courses covering exam prep content for ISTQB certification, TMMi Professional and a host of other related topics.

twitterlinkedinmail

Filed Under: Agile Testing, Testing, Transform Tagged With: Agile, Testing

About Tim Moore

Tim is a TMMi Professional and ISEB Practitioner qualified Senior Software Quality Management Consultant with 20+ years experience in software testing and quality management. An accredited TMMi Assessor with over 10 years of TMM & TMMi assessment experience. Tim leads the innovation initiatives for Experimentus, bringing new ideas, platforms, tools and ways of working to the group for consideration to include on both internal and client projects.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Take the TMMi Industry Survey
  • Take the Test Environment Management Survey
  • Take the IT Quality Lifecycle Survey

Recent Posts

  • The Human Patterns That Keep Modern IT Stuck (and the Invisible Capability We Don’t Budget For)
  • Test Environment Management : Key to Transforming Software Delivery
  • Test Process Excellence: Avoiding Pitfalls and Embracing Best Practices
  • TMMi Benefits and Outcomes – Level 4/5
  • Driving Quality: Sustainable Software Testing Insights from our 9 Month Survey Analysis

About Experimentus

We help organisations build and implement software quality processes that will enable them to measure and manage new and existing apps or systems more effectively. We deliver creative solutions – transforming not only your testing procedures, but fundamentally improving the quality of your software development process. Alongside traditional test management methods we strive to embed a culture of quality that aligns IT objectives with your business bottom line.

Recent Posts

  • The Human Patterns That Keep Modern IT Stuck (and the Invisible Capability We Don’t Budget For)
  • Test Environment Management : Key to Transforming Software Delivery
  • Test Process Excellence: Avoiding Pitfalls and Embracing Best Practices
  • TMMi Benefits and Outcomes – Level 4/5
  • Driving Quality: Sustainable Software Testing Insights from our 9 Month Survey Analysis
Request free consultation
iTM Dem
  • Home
  • Accessibility
  • Terms And Conditions
  • Privacy
  • Sitemap

Copyright © 2026 · Experimentus