I have resource slides at the end of this talk and all of the code and examples will be available on speakerdeck and githubīefore we dive into acceptance testing, we need answer an important question:.If you have any questions please hold them until the end as there is a lot of content to get through.So today we’re going to talk about Acceptance testing! What it is and what tools we have. Also, I didn’t have enough time as it’s a big subject. Why did I leave them out? Quite frankly they’re really hard to do, and to do well. I talked about Integration and Unit tests, but not Full Stack or acceptance tests. I kinda sorta left the elephant in the room. We looked at 4 types of tests White box unit tests, integration tests, Black box unit tests and characterisation tests.Īnd we also looked at how to make the your test suite as good as it could be, However… I talked about the valley of despair and the slope of enlightenment and how software testing is a skill, like mountain climbing, that can be learned and made better by practice. So cast your mind back to last year, I was up here giving my talk on “Beyond Pester 101”. This is an approximate transcript of the presentation You nailed it!!- Irwin Strachan Resources Not helpful in trying to make the sprint goal. BDD helped me to define what the MVP looks like. Now that we’re all experts there, it’s time to tackle Acceptance testing, also known as End to End testing.Īcceptance test is the bread and butter for User stories and defining your MVP. Previously in “Beyond Pester 101: Applying testing principles to PowerShell” I talked about unit and integration testing with Pester and PowerShell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |