Differences

This shows you the differences between two versions of the page.

--- bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic [2020/06/02 14:21] – external edit 127.0.0.1
+++ bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic [2020/06/04 09:13] – Removed LINKBACK hans
@@ Line 1: / Line 1: @@
 ====== "Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing" - Gojko Adzic ======
-====== Reference ======
-[[http://www.amazon.com/Bridging-Communication-Gap-Specification-Acceptance-ebook/dp/B008YZ993W?ie=UTF8&redirect=true&ref_=docs-os-doi_0|"Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing"]] by Gojko Adzic.
 ====== Review and Notes ======
@@ Line 40: / Line 37: @@
   * Tester: "You can influence the development process and stop developers from making the same mistakes over and over. You will have a much better understanding of the domain. You’ll delegate a lot of dull work to developers, who will collaborate with you on automating the verifications. You can build in quality from the start by raising concerns about possible problems before the development starts. You’ll be able to verify business rules with a touch of a button. You will have a lot more time for exploratory testing. You will be able to build better relationships with developers and business people and get their respect."
+====== Want to Know More? ======
+  * [[http://www.amazon.com/Bridging-Communication-Gap-Specification-Acceptance-ebook/dp/B008YZ993W?ie=UTF8&redirect=true&ref_=docs-os-doi_0|"Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing"]] by Gojko Adzic.
 {{tag>Book Learning Improvement AcceptanceCriteria ConditionsOfSatisfaction Review BDD ATDD}}
-~~LINKBACK~~
-~~DISCUSSION~~