{"action":"closed","issue":{"url":"https://api.github.com/repos/laboon/ebook/issues/50","labels_url":"https://api.github.com/repos/laboon/ebook/issues/50/labels{/name}","comments_url":"https://api.github.com/repos/laboon/ebook/issues/50/comments","events_url":"https://api.github.com/repos/laboon/ebook/issues/50/events","html_url":"https://github.com/laboon/ebook/issues/50","id":102879928,"number":50,"title":"Ensure all chapters receive thorough review.","user":{"login":"timparenti","id":236283,"avatar_url":"https://avatars.githubusercontent.com/u/236283?v=3","gravatar_id":"","url":"https://api.github.com/users/timparenti","html_url":"https://github.com/timparenti","followers_url":"https://api.github.com/users/timparenti/followers","following_url":"https://api.github.com/users/timparenti/following{/other_user}","gists_url":"https://api.github.com/users/timparenti/gists{/gist_id}","starred_url":"https://api.github.com/users/timparenti/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timparenti/subscriptions","organizations_url":"https://api.github.com/users/timparenti/orgs","repos_url":"https://api.github.com/users/timparenti/repos","events_url":"https://api.github.com/users/timparenti/events{/privacy}","received_events_url":"https://api.github.com/users/timparenti/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2015-08-24T20:05:24Z","updated_at":"2016-01-01T20:56:20Z","closed_at":"2016-01-01T20:56:20Z","body":"I would hate to see a situation where the first several chapters are thoroughly reviewed while the later chapters get short shrift.  It would probably be best to have at least a couple different pairs of eyes on each chapter, in addition to your own.\r\n\r\nFeel free to use and edit this list to keep track of which chapters have been reviewed in detail, and by which reviewers, so that hopefully our collective resources can best be allocated.  The checkbox doesn't so much mean \"done\" as simply \"more done than the others\".\r\n\r\n- [ ] **1.** `05` Introduction — @carols10cents #29, Patrick\r\n- [x] **2.** `10` What is Software Testing? — @carols10cents #29, @sdzivanovich #49, Patrick\r\n- [ ] **3.** `13` Why Test Software? — @carols10cents #29, Patrick\r\n- [x] **4.** `15` Testing Basics — @carols10cents #29, @sdzivanovich #49, Patrick\r\n- [ ] **5.** `20` Requirements — @carols10cents #29, @sdzivanovich #49\r\n- [ ] **6.** `25` Test Plans — @carols10cents #38\r\n- [ ] **7.** `27` Breaking Software — @carols10cents #38\r\n- [ ] **8.** `29` A Walkthrough In Creating A Test Plan — @carols10cents #38/#54\r\n- [ ] **9.** `30` Defects— @carols10cents #54\r\n- [ ] **10.** `32` Smoke And Acceptance Testing — @carols10cents #55\r\n- [ ] **11.** `33` Exploratory Testing — @carols10cents #60\r\n- [ ] **12.** `35` Manual versus Automated Testing — @carols10cents #60\r\n- [x] **13.** `40` An Introduction to Unit Testing — @sdzivanovich #57, @carols10cents #60 \r\n- [ ] **14.** `41` Advanced Unit Testing — @sdzivanovich #57, @carols10cents #70\r\n- [ ] **15.** `45` Test-Driven Development — @carols10cents #72\r\n- [ ] **16.** `50` Writing Testable Code — @carols10cents #72\r\n- [ ] **17.** `60` Pairwise and Combinatorial Testing — @carols10cents #73\r\n- [ ] **18.** `67` Stochastic and Property-Based Testing — @carols10cents #73\r\n- [ ] **19.** `70` Performance Testing — @WillEngler #19, @carols10cents #73\r\n- [ ] **20.** `75` Security Testing — @carols10cents #80\r\n- [ ] **21.** `87` Interacting with Stakeholders — @WillEngler #30, @carols10cents #84\r\n- [ ] **22.** `96` Conclusion — @carols10cents #84\r\n- [ ] **23.** `97` Testing Templates\r\n- [ ] **24.** `98` Glossary of Terms — @carols10cents #84\r\n- [ ] **25.** `99` Acknowledgements"}}