Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Add checks to each scenario to ensure push server returns proper HTTP status codes #73

Open
rpappalax opened this issue Oct 4, 2016 · 0 comments
Assignees

Comments

@rpappalax
Copy link
Contributor

rpappalax commented Oct 4, 2016

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.

@rpappalax rpappalax added the p2 label Oct 4, 2016
@bbangert bbangert added the ready label Oct 20, 2016
@pjenvey pjenvey self-assigned this Oct 20, 2016
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Nov 10, 2016
@bbangert bbangert added p1 and removed p2 labels Nov 14, 2016
@pjenvey pjenvey added the p2 label Apr 12, 2017
@jrconlin jrconlin removed the p1 label Apr 12, 2017
@pjenvey pjenvey added p1 p2 and removed p2 p1 labels Apr 12, 2017
@bbangert bbangert added p1 and removed p2 labels May 31, 2017
@bbangert bbangert added p2 and removed p1 labels Aug 2, 2017
@bbangert bbangert added p1 and removed p2 labels Jun 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants