tests/app/main/views/test_tour.py

import pytest
from flask import url_for

import app


@pytest.mark.parametrize("page", range(1, 5))
def test_should_render_tour_pages(
    app_,
    api_user_active,
    mocker,
    mock_get_service,
    page
):
    with app_.test_request_context():
        with app_.test_client() as client:
            response = client.get(url_for('main.tour', page=page))
            assert response.status_code == 200
            assert 'Next' in response.get_data(as_text=True)
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119 2016-04-01 10:54:55 +01:00			`import pytest`
			`from flask import url_for`

			`import app`


			`@pytest.mark.parametrize("page", range(1, 5))`
			`def test_should_render_tour_pages(`
			`app_,`
			`api_user_active,`
			`mocker,`
Added current_service to flask context and template context. Fix all tests and conflicts. Removed comment line. 2016-04-04 16:53:52 +01:00			`mock_get_service,`
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119 2016-04-01 10:54:55 +01:00			`page`
			`):`
			`with app_.test_request_context():`
			`with app_.test_client() as client:`
Make tour work for non-logged-in users There’s no content in the tour that’s specific to a service. And since we can now take a pretty good guess at what service you last used, or which service we should send you to if you only have one service, there’s no need to make the URLs for the tour service-specific. This also means that you don’t need to be logged in to see the tour pages, and we have no good reason to only restrict these pages to users with accounts. https://www.pivotaltracker.com/story/show/116960703 2016-04-19 10:30:15 +01:00			`response = client.get(url_for('main.tour', page=page))`
Show a tour when users first create a service This commit adds a 3 screen tour, similar to those used on GOV.UK Verify and Passports. We guerilla tested this on Friday, and it really helped users to build a mental model of how Notify works, so that when they’re playing around with it they have a greater sense of what they’re aiming to do. This makes concepts like templates and placeholders click more quickly. https://www.pivotaltracker.com/story/show/116710119 2016-04-01 10:54:55 +01:00			`assert response.status_code == 200`
			`assert 'Next' in response.get_data(as_text=True)`