New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 701527 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

add basic http 200 check to pre-prod test

Project Member Reported by akes...@chromium.org, Mar 14 2017

Issue description

Inspired by https://bugs.chromium.org/p/chromium/issues/detail?id=698773 (however, not sure this will actually address that problem, because the error wasn't on the create job page, but on a javascript action from a button on that page?)

Add a basic test in the push to prod that runs curl against a few URLs of the autotest web UI, and ensures that they return http-200.

This protects us against pushes that catastrophically break the autotest UI.

As I said though, I'm not sure this would actually have protected us in 698773
 
Cc: krisr@chromium.org
sbasi@ corrects me, the page was in fact broken without need to push a js button
Bonus points: an autotest that we add to the moblab_quick test suite, so that we can also catch these problems in the CQ.
Cc: chingcodes@chromium.org
Status: Archived (was: Untriaged)
This bug is very old, is Untriaged, and has no owner.  If it is still relevant, reopen as Untriaged or open a new bug

Sign in to add a comment