devdocs/todo.txt

@@ -64,8 +64,12 @@ and backend.  I want to know what happens under typical heavy usage simulating m
 I'm guessing something that autodrives a browser or simulates one to access via client UI for full end to end testing.
 	- Should be configurable to simulate various loads:
 		- Smoke test (Quick bug test): excercises one of everything once only looking for fundamental problems
-		- Load test (Slower longer test to look for scaling issues related to a huge, busy office): exercises typical daily load of very large office but configurable to run in simulated days, so
-			can run it as a simulated week with 7 or month with 30 or years by entering in the number of days to simulate.  Would be nice if it did month end type stuff or delayed then billed out etc.
+		- Load / scale / assurance test (Slower longer test to look for scaling issues related to a huge, busy office): exercises typical daily load of very large office but configurable to run in simulated days, so
+			can run it as a simulated week with 7 or month with 30 or years by entering in the number of days to simulate.  
+			Would be nice if it did month end type stuff or delayed then billed out etc.
+			Should report stats about timing etc from the client perspective, we already have metrics for the backend perspective.
+				I'd like to know immediately if something is weirdly slow, not just in error.
+			Should not erase data at end so we can then manually login and check things out with a full load of at scale data