Closed m1yag1 closed 6 years ago
Stack OverflowCurrently our web application takes around 3 mins to load completely without caching and 10 secs with caching. When I open the app through WebDriver its taking around 3 mins to load i.e. caching is...
I see 2 possible solutions for local tests. Will not work on Travis because we cannot persist the cache there.
Solution A: Add a flag (such as --cache
) and require the tester to run the tests both before and after the deployment with the flag set.
Solution B: Always enable caching by default.
When caching is enabled, we will set the Chrome profile path to a fixed path in the filesystem. That should enable caching. Will require changes to the legacy tests that always assume the user is not logged in at the beginning.
This answer to a different issue may allow us to specify the profile by name instead of path: https://stackoverflow.com/a/6830109
Stack OverflowI am using Selenium Web Driver API with Java. Every time I want to debug my test cases, a temporary profile for Firefox is created in the temporary files directory. This is a headache in two ways. ...
😄 This was originally written as just a reminder to the manual tester. But I'm glad we're thinking about caching issues (and how to automate testing them).
Closing issue as I don't think we'll get around to this anytime soon. We can re-open when the need arises.
REMINDER: Check for new user-facing features in a browser that has previously cached data from webview -- especially js, css, images. Do NOT use an incognito or private browser.
The idea is to replicate an end user experience and catch any problems that may arise due to caching issues.