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.

Sign up for GitHub

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

Jump to bottom

beforeAll fixture hook #3517

Closed
qualityshepherd opened this issue Mar 3, 2019 · 2 comments
Closed

beforeAll fixture hook #3517

qualityshepherd opened this issue Mar 3, 2019 · 2 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.

Comments

@qualityshepherd
Copy link

What is your Test Scenario?

I need the ability to perform some actions in a browser before all tests. Sadly, before doesn't have browser access and some actions you do not want to be repeated each test like in a beforeEach. Currently, my only solution is to couple tests or waste time with unneeded, repeated steps.

What are you suggesting?

A beforeAll hook that is fired only once per fixture.

What alternatives have you considered?

I've tried hacky ways to have things in bforeEach only fire once... but why not just have a beforeAll?

Additional context
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 3, 2019
@Farfurix
Copy link
Contributor

Farfurix commented Mar 4, 2019

@qualityshepherd,

Hello. Our team will process your feature request in the context of #1345.

@Farfurix Farfurix closed this as completed Mar 4, 2019
@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 4, 2019
@lock
Copy link

lock bot commented Mar 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@qualityshepherd @Farfurix