testing

Use Case Driven Testing. Part IV

Use Case Driven Testing. Part IV

The second element of the SAFe Continuous Delivery Pipeline (CDP) is Continuous Integration (CI). This is where top priority features for a program increment get decomposed into stories. I recommend the use of Use Case for feature decomposition (into stories), design, and testing. Use Case Driven Design, Build, Test: decomposing a feature into pint-sized stories using Use Case comes naturally: it has an Actor and a Use Case (a need). Example: As a family man with a young family, I would need a people-mover van, so that the whole family can go to short trips on weekends. It has an…
Read More
Use Case Driven Testing. Part III

Use Case Driven Testing. Part III

Assume that we have an approved initiative, idea, or an epic. What follows next in SAFe' Continuous Delivery Pipeline is its first element, Continuous Exploration (CE). Use Case Driven Analysis: CE is our opportunity to analyze and flesh out the Minimum Viable Product (MVP) as described in the approved idea's Lean Business Case. Features are the artifacts of CE.. together with clearer vision of the product and a roadmap of features -- could be laid out across multiple Program Increments (PI) -- to make the product vision a reality. Use UCM to delimit the system: Use Case Modeling (UCM) is…
Read More

Use Case Driven Testing. Part II.

There are three cornerstones of Use Case Engineering (UCE): 1) Analysis; 2) Design; 3) Certify. That is: Analyze the users needs Design to fit those needs Certify that the needs are fulfilled Guess what? Needs are Use Cases! Whether you are analyzing, designing for implementation of the Use Cases or certifying/testing using Use Cases (remember, Use Cases are Test Cases!), Use Cases are driving these activities. Lean Agile Story (and feature for that matter) is from a user's perspective given a certain scenario (scenario is an interesting instance of a Use Case) that brings a perceived value/benefit to the user.…
Read More

Use Case Driven Testing

I am biased towards the usage of Use Case Engineering (UCE) ... be it usage in analysis, design, or testing. One of the reasons why ... is the fact that every Use Case is, in fact, a: 1) story (yeah, just like a Use Case, a story or scenario is told from an Actor's (a Persona's) perspective vis-a-vis his/her interaction with a system; 2) a Test Case (yeah, a famous mantra from the Use Case-universe is this : 'Use Cases are Test Cases'! Let's take a step back to take a wider perspective of this UCE ... to appreciate and…
Read More

Testing in Lean Agile World. Part III

When it comes to TDD and BDD, the acronym MECE comes to mind: Mutually Exclusive, Collectively Exhaustive. TDD (Test Driven Development): Stories -- just like Objects in the Object Oriented world -- are independent... self-contained and meaningful on their own -- all stories have a sense of exclusiveness. All stories are mutually exclusive and each can be tested as a unit. In TDD, a rich set of Unit Test scripts are written and ran... failures are observed ...write code to pass the tests ... run all tests again and observe pass / fail ... then refactor as necessary. This rich…
Read More
Testing in Lean Agile World. Part II

Testing in Lean Agile World. Part II

TDD, BDD and ATTD...do these acronyms ring a bell? SAFe certainly brought these on the SAFe forefront with their 4.6 release: Test Driven Development (TDD), Behavior Driven Development (BDD), Acceptance Test Driven Development (ATTD). These are not new. SAFe just added these with the intent of having more focus on testing and quality as part of SAFe 4.6. About time! Previous SAFe versions had weak treatment of testing ... until now. Let's look at TDD ... at a SAFe team-level. To be continued...
Read More
Testing in Lean Agile World

Testing in Lean Agile World

'If stories are the workhorse of agile development -- the key proxy artifact that carries the value stream to the customer -- then story acceptance tests are the workhorse of agile testing...' -- Dean Leffingwell. What does this mean specifically vis-a-vis SAFe 4.6 ? To be continued...
Read More
Test Acceptance Criteria

Test Acceptance Criteria

SAFe 4.6 was officially released on November 14, 2018. In my first glance that day, it looked like, from the surface, a small incremental update to SAFe 4.5. Looking into it, at a deeper dive days after the release, it is more substantial than I earlier first thought... and it made SAFe better! Much better! Let's start with testing. Stories from now on not just need acceptance criteria... it must now have test acceptance criteria. This move is a step towards the right direction of producing quality system. Hello, TDD (Test Driven Development)! How about features? Yes, there is behavior…
Read More
X

Forgot Password?

Join Us