Skip to content
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

Re-add tests for loading the last URL visited by the app #316

Open
jkuester opened this issue Jun 1, 2023 · 1 comment
Open

Re-add tests for loading the last URL visited by the app #316

jkuester opened this issue Jun 1, 2023 · 1 comment
Labels
Type: Technical issue Improve something that users won't notice

Comments

@jkuester
Copy link
Contributor

jkuester commented Jun 1, 2023

#315 deleted the LastUrlTest.java file which was a UI Test (Android test):

Test that when the app is closed and then opened again, the last URL viewed is loaded instead of the app URL.

Unfortunately, these UI tests have not been properly running since #236 when changes to the brand naming (dropping Webapp) meant that the make commands for the UI tests would complete successfully, but no tests would actually get run. Then, #252 removed the DISABLE_APP_URL_VALIDATION functionality that was required for the LastUrlTest. (Since the UI tests were not actually running, we did not realize at the time that it was required for the test...)

I have considered simply re-adding DISABLE_APP_URL_VALIDATION so that the LastUrlTest can run, but that flag is essentially an obscene hack that would only be useful for this hacky test case. Instead, I am just removing the test in #315 and logging this issue so that someone (aka future me) can go figure out a better way to do this test that does not involve hacking all over the implementation code....

@jkuester jkuester added the Type: Technical issue Improve something that users won't notice label Jun 1, 2023
@jkuester
Copy link
Contributor Author

jkuester commented Jun 2, 2023

To provide a little more detail here, the reason this test does not work without DISABLE_APP_URL_VALIDATION is because it relied on using a custom url (https://angular.io/start) that was not a CHT instance at all. I think this test should be re-written to just connect to a proper CHT instance. The non-trivial part is that this probably involves spinning up a test instance to connect to as part of the test suite...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

1 participant