Skip to content

Commit

Permalink
Merge pull request #1650 from alphagov/update-survey-doc
Browse files Browse the repository at this point in the history
Update Testing surveys doc
  • Loading branch information
AgaDufrat authored Mar 14, 2019
2 parents 8d57e9d + 32895ae commit 529ae54
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions doc/surveys.md
Original file line number Diff line number Diff line change
Expand Up @@ -239,9 +239,9 @@ We record how many times a given survey is shown to a user and won't show it aga
You can test if the surveys work locally by starting up the various rendering apps needed for the GOVUK page that you want the survey to be appear on. e.g.
A link for "government/policies" requires the `finder-frontend` app, so you would need to call `bowl finder-frontend` in the development VM. You can check which rendering app is needed by going to `www.gov.uk/api/content/<path here>`, e.g. `www.gov.uk/api/content/government/policies`

Usually it would be enough to call `bowl government-frontend finder-frontend whitehall router`
Usually it would be enough to call `bowl frontend government-frontend finder-frontend whitehall router`

The `router` at the end allows you to access the link by `www.dev.gov.uk` in your browser. Following on from the previous example you could go to `www.dev.org.uk/government/policies` to check if the survey will appear.
The `router` at the end allows you to access the link by `www.dev.gov.uk` in your browser. Following on from the previous example you could go to `www.dev.gov.uk/government/policies` to check if the survey will appear.

You can check if the `activeWhen paths` for your survey are correct by typing `GOVUK.userSurveys.pathMatch(<insert path here>)` into the browser console on the page. A return of `true` indicates that path matches.

Expand Down

0 comments on commit 529ae54

Please sign in to comment.