QuestionQ253

Building and testing applications

For this question, refer to the HipLocal case study.

How can HipLocal accelerate API development while continuing to provide the QA team with a stable testing environment that fulfills feature requirements?

  • A Include unit tests in their code, and prevent deployments to QA until all tests have a passing status.
  • B Include performance tests in their code, and prevent deployments to QA until all tests have a passing status.
  • C Create health checks for the QA environment, and redeploy the APIs at a later time if the environment is unhealthy.
  • D Redeploy the APIs to App Engine using Traffic Splitting. Do not move QA traffic to the new versions if errors are found.
Explanation

The HipLocal case study notes that release cycles include development freezes to allow for QA testing and that HipLocal needs faster, more accurate validation of new features. Gating deployments on unit tests (failing the build and blocking promotion to QA whenever a test fails) lets developers commit and iterate continuously while guaranteeing that only functionally correct code ever reaches the QA environment, so QA always has a stable build that reflects the intended feature set. Performance tests, environment health checks, and App Engine traffic splitting address non-functional or rollout concerns, not whether the code deployed to QA actually implements the required features correctly.

Community Discussion

No comments yet. Be the first to start the discussion!