admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-12-21 20:10:19 +00:00
parent 66fb71bf65
commit b55818ea63
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
devdocs/deploy.txt
View File

@@ -42,14 +42,16 @@ BASELINE WHAT TO CHECK:
DASHBOARD PAGE is the main page with the main stats: DASHBOARD PAGE is the main page with the main stats:
"REquests summary" "REquests summary"
The most telling overall stat is the "Requests summary" pie chart pass/fail ratio on the main page 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% As of today 2021-12-21 release 8-beta.06 the results are PASS: 92.87%, FAIL: 7.13%
(however they are all in the report render so need to look into that something wrong in the test) Errors *are* expected, it's a stress / load test but there shouldn't be an entirely failing route, just a scattered set of failures,
typically unauthorized or bad gateway
"Appdex" - skipping this for now, not really relevant at the moment "Appdex" - skipping this for now, not really relevant at the moment
"STATISTICS" table - this is the important one as it shows failures "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. - Scroll down and look in "executions" -> "FAIL" column and make sure they are not all in one line item
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 if see a lot of failures in a single route need to manually look into that exact issue and route and examine the jmeter test for that route / run it manually perhaps
it's normal to see unauthorized or bad gateway errors when the server is super stressed out but other failures might need examination or all of it if less than 90% success
@@ -58,7 +60,7 @@ NOTES:
- this also catches reporting as it generates some reports - 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 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. 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" - 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: 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"> <ConfigTestElement guiclass="HttpDefaultsGui" testclass="ConfigTestElement" testname="Devops request defaults" enabled="true">