Forum Discussion
Hi,
> When I execute this test in non-incognito modus it fails
To add to tristaanogre:
While it is a matter of requirements to your tests and test code and the actual failure context, you may consider to improve your tests so that they do not fail. For example, for the classic unit test it may be required to have an empty input field on test start. And this is quite fine for the unit test. But for the end-to-end test that more or less emulates how the end-user works with your application: if the browser in standard configuration pre-fills input fields with previous data and this creates problems for the end-user (read this as 'breaks your test') then this may be the reason to reconsider how your application is implemented.
AlexKarasThankyou for the addition, I think that is a quite valueble addition which I hadn't thought of yet.
The only problem here for me is, that the function tristaanogre described indeed seemed to be enabled in chrome, but it didn't prefill any field with any value.
At least as far as I could see it were always just empty textfields and there was no possible value given.
That's why I asked how one could start the incognito modus, so that I at least know that I am not messing with an older build of the page or whatever. At this moment I don't care about the prefilling. It should not prefill and all I want to know at first is that the page is working normally when you get there for the first time.
- AlexKaras7 years agoChampion Level 3
Hi,
Then, as it was mentioned by Robert, the simplest way to start Chrome in Incognito is to add it to Tested Applications and provide necessary start parameters.
Then, for example, you may change your test that it starts Chrome via TestedApps.Run() call, navigate to the required address, get opened page and continue as usual.
Related Content
Recent Discussions
- 6 hours agoashly