You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
As-is, ap-loadtester can be used as a blunt-instrument to 'hammer' autopush in a variety of scenarios at scale. If the server falls over or throws a traceback, that's the closest thing to a "fail" that we can currently measure. The closest thing to a test "pass" is the absence of a traceback.
Ideally, (for API testing), we'd walk through the various scenarios and ensure that autopush returns us the HTTP status code(s) we expect with each step. Currently the only way this information could be accessed would be tracing a given test all the way back through Kibana.
The text was updated successfully, but these errors were encountered:
As-is, ap-loadtester can be used as a blunt-instrument to 'hammer' autopush in a variety of scenarios at scale. If the server falls over or throws a traceback, that's the closest thing to a "fail" that we can currently measure. The closest thing to a test "pass" is the absence of a traceback.
Ideally, (for API testing), we'd walk through the various scenarios and ensure that autopush returns us the HTTP status code(s) we expect with each step. Currently the only way this information could be accessed would be tracing a given test all the way back through Kibana.
The text was updated successfully, but these errors were encountered: