devdocs/deploy.txt

@@ -32,11 +32,40 @@ Once tests pass move on to next step
 ### Run load tests against Linux and Windows servers
 (determine if any changes triggered performance issues, needs baseline comparison value)
 
-To test local or devops edit the project file "C:\data\code\raven-test\load\stressdevops.jmx"
+STEPS:
+Login to server to test and seed fresh data first, then can run this test
+run C:\data\code\raven-test\load\runtest.bat 
+Test will take approximately 14 minutes to run
+Check results in results folder by opening index.html from windows explorer and view in browser
+
+BASELINE WHAT TO CHECK:
+DASHBOARD PAGE is the main page with the main stats:
+"REquests summary"
+The most telling overall stat is the "Requests summary" pie chart pass/fail ratio on the main page 
+As of today 2021-12-21 release 8-beta.06 the results are PASS: 99.04%, FAIL: 0.96% 
+(however they are all in the report render so need to look into that something wrong in the test)
+
+"Appdex" - skipping this for now, not really relevant at the moment
+
+"STATISTICS" table - this is the important one as it shows failures
+- Scroll down and look in "executions" -> "FAIL" column and make sure they are not all in one line item or more than a tiny pct.
+  if see a lot of failures need to manually look into that exact issue and route and examine the jmeter test for that route / run it manually perhaps
+
+
+
+
+NOTES:
+- this also catches reporting as it generates some reports
+  report-render test has explicit report id number for workorder, currently it's 15 for the dispatch report, if all fail it may have changed the id number
+  would be better deterministically but for now this works.
+  
+- To test local or devops edit the project file "C:\data\code\raven-test\load\stressdevops.jmx"
 There are two configuration sections near top for local or devops and it's switched by setting either enabled or disabled:
 <ConfigTestElement guiclass="HttpDefaultsGui" testclass="ConfigTestElement" testname="Devops request defaults" enabled="true">
 or
  <ConfigTestElement guiclass="HttpDefaultsGui" testclass="ConfigTestElement" testname="Localhost request defaults" enabled="false">
+- Load test needs fresh seeding so it can create test users.
+-
 
 Once tests pass within expected parameters move on to next step