-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add React router tests #430
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
<!doctype html> | ||
<html> | ||
<head> | ||
<script> | ||
window.condaStoreConfig = { | ||
REACT_APP_ROUTER_TYPE: "memory" | ||
}; | ||
</script> | ||
</head> | ||
<body> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
"""Test app with different types of React routers | ||
|
||
- browser router (uses the history API) | ||
- memory router (uses in-app memory) | ||
|
||
Ref: https://reactrouter.com/en/main/routers/create-memory-router | ||
""" | ||
|
||
import pytest | ||
import re | ||
from playwright.sync_api import Page, expect | ||
|
||
|
||
@pytest.fixture | ||
def test_config(): | ||
return {"base_url": "http://localhost:8000"} | ||
|
||
|
||
def test_browser_router_200_ok(page: Page, test_config): | ||
"""With browser router, a known route should show the corresponding view | ||
""" | ||
# Check that when going to a known route (in this case, the route to create | ||
# a new environment), the app loads the view for that route. | ||
page.goto(test_config["base_url"] + "/default/new-environment") | ||
|
||
# We know we are at the correct view (i.e., new environment form) if there | ||
# is a textbox to enter the name of the new environment. | ||
expect(page.get_by_role("textbox", name="environment name")).to_be_visible() | ||
|
||
|
||
def test_memory_router_200_ok(): | ||
"""With memory router, all routes are 200 (OK) so there's nothing to test there | ||
""" | ||
pass | ||
|
||
|
||
def test_browser_router_404_not_found(page: Page, test_config): | ||
"""With browser router, an unknown route should result in a 404 not found error | ||
""" | ||
page.goto(test_config["base_url"] + "/this-is-not-an-app-route") | ||
expect(page.get_by_text("404")).to_be_visible() | ||
|
||
|
||
def test_memory_router_404_not_found(page: Page, test_config): | ||
"""The memory router has been configured to load the root view at any route | ||
""" | ||
# The route `/memory-router-test.html` is not a route recognized by the | ||
# React app. With the browser router, an unknown route would give a 404. | ||
page.goto(test_config["base_url"] + "/memory-router-test.html") | ||
expect(page.get_by_test_id("no-environment-selected")).to_be_visible() | ||
|
||
|
||
def test_browser_router_updates_location(page: Page, test_config): | ||
"""With browser router, following a link should update browser URL | ||
""" | ||
# Go to root view and verify that it loaded | ||
page.goto(test_config["base_url"]) | ||
expect(page.get_by_test_id("no-environment-selected")).to_be_visible() | ||
|
||
# Get and click link to "create new environment" | ||
page.get_by_role("button", name="default").get_by_role( | ||
"link", | ||
# Note the accessible name is determined by the aria-label, | ||
# not the link text | ||
name=re.compile("new.*environment", re.IGNORECASE), | ||
).click() | ||
|
||
# With browser router, the window location should update in response to | ||
# clicking an app link | ||
expect(page).to_have_url(re.compile("/default/new-environment")) | ||
|
||
|
||
def test_memory_router_does_not_update_location(page: Page, test_config): | ||
"""With memory router, following a link should NOT update browser URL | ||
""" | ||
page.goto(test_config["base_url"] + "/memory-router-test.html") | ||
|
||
# Get and click link to "create new environment" | ||
page.get_by_role("button", name="default").get_by_role( | ||
"link", | ||
# Note the accessible name is determined by the aria-label, | ||
# not the link text | ||
name=re.compile("new.*environment", re.IGNORECASE), | ||
).click() | ||
|
||
# With memory router, the window location should **not** update in response | ||
# to clicking an app link | ||
expect(page).to_have_url(re.compile("/memory-router-test.html")) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, I tried looking at the
Response
object returned bypage.goto
and found that the response code was 200 (OK). Do we expect it to be 404 here? It might be a more robust way of checking the right response, maybe in addition toget_by_text('404')
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, hm, yeah, that is confusing.
I have actually forgotten best practices for this.
I recently created a related conda-store server issue about creating a catch-all route that returns the UI app instead of a 404, if no other route is matched.
I will have to do some research, but I think that ultimately if we want an actual HTTP 404 status code, we will have to define the UI app routes in both the client-side and server-side code.
The only reason these nonsense routes, such as /foo-bar, return the UI app with a 200, by the way, is because of the
--history-api-fallback
Webpack dev server flag passed to the package.jsonstart
script:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the error code itself is intended behavior of
--history-api-fallback
. Is that good/what we want? Seems like invalid routes should return error codes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm? I'm not sure I follow. In the example you pasted above, the
--history-api-fallback
flag is precisely why/foo/bar
returns 200 (with the app bundle) instead of a 404.I did some web searching and I discovered that one solution (that doesn't require us to find a way to share routes between the front end and the back end) is to do a JavaScript redirect to a 404/not-found page when the user goes to an unknown route. Here's how that would work, step by step:
window.location = "/not-found"
Does that make sense? It's a little less than ideal. But the ideal solution requires us to either duplicate or share the React app routes between both the front-end and back-end codebases.