Reputation: 3
We are introducing E2E tests in some of our Single Page Applications (SPA) and are really inclined towards using testcafe for it. Since SPA's take a long time to load and provide fast subsequent navigation we are using experimental disablePageReload feature in testcafe because without it the tests take too much time to be usable.
I followed this issue #1770 and wanted to ask this question there but the comments have been disabled.
On the issues mentioned by a collaborator in the link above on why this feature is experimental, my thoughts are as below (collaborator comment with my thoughts)
We assume that it's hard to write tests so that they don't require page reloads, which makes this feature difficult to use.
We think that writing tests in such a way affect their stability.
There are some aspects of this feature that aren't finished yet. For example, using this feature when tests are run concurrently.
I only want to know, if there is some direction on this feature to be officially implemented or this will be removed eventually. It's very important for the decision at my company.
Upvotes: 0
Views: 422
Reputation: 1036
Thank you for sharing your own view of this feature. Currently, we still receive messages from users interested in its official implementation. So, we decided to continue working on developing this functionality, but, at the moment, I cannot give you any estimates on when the feature will be published.
Upvotes: 1