fixed typos in sprint dates, added works fe and be in testing section…

… of rubric
neu-se · Mar 26, 2024 · 1eb6e83 · 1eb6e83
1 parent c43250d
commit 1eb6e83
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/Assignments/project-grading.md b/Assignments/project-grading.md
@@ -52,7 +52,7 @@ We will grade each of these using the following rubric:
 * Implemented feature does not include any eslint-disable or ts-ignore flag
 
 ### Testing (10%)
-The project must include evidence of testing. Ideally, all new features will be accompanied by fully automated tests, but in some circumstances (particularly when engaging with Phaser, the game library, or Tiled, the map editor), this may not be feasible. If automated tests are not possible, include a discussion of your manual testing strategy, including a script that a future developer could use to manually test the feature. There is no explicit requirement to make use of any specific testing technology (e.g. mocks, spies, etc.).
+The project must include evidence of testing (both for front-end and back-end). Ideally, all new features will be accompanied by fully automated tests, but in some circumstances (particularly when engaging with Phaser, the game library, or Tiled, the map editor), this may not be feasible. If automated tests are not possible, include a discussion of your manual testing strategy, including a script that a future developer could use to manually test the feature. There is no explicit requirement to make use of any specific testing technology (e.g. mocks, spies, etc.).
 
 #### Satisfactory:
 * Any new or modified backend features include tests that validate that the feature works as intended. These tests cover the changed code, and also contain well-written assertions that thoroughly check the expected behaviors.

diff --git a/Assignments/project-plan.md b/Assignments/project-plan.md
@@ -93,8 +93,8 @@ Each work item should contain the following information:
 * Milestone for delivering the task, chosen from one of the following:
   * Sprint 0: Feb 14-Feb 28
   * Sprint 1: Feb 29-Mar 13 (Sprint 1 is just a single week, not including spring break)
-  * Sprint 2: Mar 14-Mar 28
-  * Sprint 3: Mar 29-Apr 10
+  * Sprint 2: Mar 14-Mar 27
+  * Sprint 3: Mar 28-Apr 10
 
 Your work breakdown should take the format of a simple textual list.
 

diff --git a/Assignments/revised-project-plan.md b/Assignments/revised-project-plan.md
@@ -72,8 +72,8 @@ Each work item should contain the following information:
 * Milestone for delivering the task, chosen from one of the following:
   * Sprint 0: Feb 14-Feb 28
   * Sprint 1: Feb 29-Mar 13 (Sprint 1 is just a single week, not including spring break)
-  * Sprint 2: Mar 14-Mar 28
-  * Sprint 3: Mar 29-Apr 10
+  * Sprint 2: Mar 14-Mar 27
+  * Sprint 3: Mar 28-Apr 10
 
 Your work breakdown may take the format of a simple textual list.