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

execute navigateTo automatically for every test #11

Closed
DaniRey opened this issue Oct 21, 2016 · 1 comment
Closed

execute navigateTo automatically for every test #11

DaniRey opened this issue Oct 21, 2016 · 1 comment
Assignees

Comments

@DaniRey
Copy link
Collaborator

DaniRey commented Oct 21, 2016

Often multiple tests are chained together using the it keyword. When doing so, usually only the first spec contains a navigateTo(url) call. When only starting a single test, which isn't the first one, the test fails, because navigateTo is not called.

We should provide an easy way to configure a URL which is then used for all tests. Depending on the situation, the test suite should automatically call navigateTo befor the test, no matter wheter all or only a single test is executed.

@DaniRey DaniRey self-assigned this Oct 23, 2016
DaniRey pushed a commit that referenced this issue Oct 23, 2016
the path can now be defined as part of the spec. The IntegrationSpec will then execute "go to" before each test, using the stored url (defined as $host$projectRoot$path). If some tests need to change the path, they might do so by calling the afterChangingPathTo method.
@DaniRey DaniRey closed this as completed Oct 23, 2016
@DaniRey DaniRey reopened this Oct 24, 2016
@DaniRey
Copy link
Collaborator Author

DaniRey commented Oct 24, 2016

Implementation was unnecessary complex, therefore reopening

DaniRey pushed a commit that referenced this issue Oct 24, 2016
 simplified implementation and providing more control on navigateTo execution
@DaniRey DaniRey closed this as completed Oct 24, 2016
DaniRey pushed a commit that referenced this issue Oct 24, 2016
 added test for enforceNavigateTo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant