From c893aa99b469bf84b1474117406482937ba81c19 Mon Sep 17 00:00:00 2001 From: Jared Grippe Date: Thu, 27 Apr 2017 15:40:59 -0700 Subject: [PATCH 1/2] feedback for 283 --- _goals/283-Concept_Focus-Testing_and_TDD.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_goals/283-Concept_Focus-Testing_and_TDD.md b/_goals/283-Concept_Focus-Testing_and_TDD.md index 95bcdd14..55d101c6 100644 --- a/_goals/283-Concept_Focus-Testing_and_TDD.md +++ b/_goals/283-Concept_Focus-Testing_and_TDD.md @@ -12,6 +12,10 @@ published: true redirect_from: '/goals/283' --- +__FEEDBACK:__ I think we should move this goal back into draft. Look at it from the perspectice of consistant and objective completeness scores, I conclude the specs are too ambigious. + +__RECOMMENDATION:__ This goal should come with an app that needs testing and at least one example of each kind of test so the learner can follow a pre-existing example. This goal currently says "go figure out how these three kinds of tests work and impliment them" which is too large of an ask for one week at any skill level. I doubt I could complete this goal in a way jrob would give me 100%. The lines between unit, integration and feature tests is ambigious even among experts. I think if we provide an example learners can follow this will be a more objectively measurable way to practice writing these kinds of tests. + # Concept Focus: Testing and TDD ## Challenge Rating From 7ed32c59b045e6a59186b5d343997692857e3077 Mon Sep 17 00:00:00 2001 From: Jared Grippe Date: Thu, 27 Apr 2017 15:41:57 -0700 Subject: [PATCH 2/2] Update 283-Concept_Focus-Testing_and_TDD.md --- _goals/283-Concept_Focus-Testing_and_TDD.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_goals/283-Concept_Focus-Testing_and_TDD.md b/_goals/283-Concept_Focus-Testing_and_TDD.md index 55d101c6..71f40091 100644 --- a/_goals/283-Concept_Focus-Testing_and_TDD.md +++ b/_goals/283-Concept_Focus-Testing_and_TDD.md @@ -66,6 +66,8 @@ An added benefit of working on a concept-focus goal is that you'll have a projec ## Specifications +__FEEDBACK:__ all the `Examples … listed and linked to in the README.` specs are confusing. What is a link? Can we have an example? + - [ ] Artifact produced is a GitHub repo. - [ ] Repo contains a full-stack web application using Node.js. - [ ] Application uses a database.