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

Divide execution of fast and slow tests. #639

Closed
ArtemijRodionov opened this issue Nov 24, 2018 · 2 comments
Closed

Divide execution of fast and slow tests. #639

ArtemijRodionov opened this issue Nov 24, 2018 · 2 comments
Assignees
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable devops work with service options with code or with configs report Put it to completed tasks temporary list for business

Comments

@ArtemijRodionov
Copy link
Contributor

Stop a build process if fast tests fail. This will decrease tests execution time

We already have implemented this in STB.
See this: fidals/stroyprombeton#348 and fidals/stroyprombeton#358

@ArtemijRodionov ArtemijRodionov added 1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable devops work with service options with code or with configs labels Nov 24, 2018
@ArtemijRodionov ArtemijRodionov self-assigned this Nov 24, 2018
ArtemijRodionov added a commit that referenced this issue Nov 28, 2018
Create runner and todo for it

Tag tests

Apply linter rules
@0pdd
Copy link
Collaborator

0pdd commented Nov 28, 2018

@artemiy312 the puzzle #647 is still not solved.

@0pdd
Copy link
Collaborator

0pdd commented Dec 1, 2018

@artemiy312 the only puzzle #647 is solved here.

@ArtemijRodionov ArtemijRodionov added the report Put it to completed tasks temporary list for business label Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable devops work with service options with code or with configs report Put it to completed tasks temporary list for business
Projects
None yet
Development

No branches or pull requests

2 participants