So before we get going here, here are the steps I am going to be walking you through.I’ll be walking through those as I am going back and forth to the diagram over here.What I’m going to do is I’m gonna create a feature that really talks about if I were to remove something from a system, or I would deduct an item from our inventory, what it’s going to do is it’s actually going to go through this behavior of the system.
Where then we can actually get into a release readiness to push to prod.” Okay so now let’s go back. Okay so now we’ve gone through the whole failing part. So now I’m going to implement my automated steps, right? So in step five, I would implement my code for this feature to behave as and I also implement my automated steps that would tie back to the test scenarios that go on in my acceptance criteria.
One of the things that people don’t really understand a lot of times is that people think that when you do behavior and development, you use something a tool like cucumber.
We are going to fast fail the features into source code.
So getting back to what we talked about last week, right?
And on that user story what I am going to do is, I’ve got acceptance criteria that’s been documented in a feature format.
So when we talk about using feature files, that’s really the file type that’s used by lots of behavior-driven development frameworks like Cucumber, like some of the other ones out there like Spec Flow.But we are going to be using a couple of things here that some of you all maybe familiar with.Some of you may not be, but let’s just talk through some of the tools that are going to be in place.And lastly, we are going to be using Cucumber as our manager and development framework.That’s also got some acceptance testing kind of baked in there to do the actual testing before we release into production.Or it can make you really excited about talking about Dev Ops.