Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

Divide execution of fast and slow tests. #348

Closed
ArtemijRodionov opened this issue Nov 18, 2018 · 3 comments
Closed

Divide execution of fast and slow tests. #348

ArtemijRodionov opened this issue Nov 18, 2018 · 3 comments
Assignees
Labels
2 performer can implement issue at his closest convenient time 30 mins small issues. Usually cosmetic fixes 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

ArtemijRodionov commented Nov 18, 2018

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

@ArtemijRodionov ArtemijRodionov added 30 mins small issues. Usually cosmetic fixes 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 18, 2018
@ArtemijRodionov ArtemijRodionov self-assigned this Nov 18, 2018
@ArtemijRodionov ArtemijRodionov changed the title Divide execution of unit and selenium tests. Divide execution of fast and slow tests. Nov 18, 2018
@duker33
Copy link
Contributor

duker33 commented Nov 19, 2018

@artemiy312 , create the same task for SE plz

ArtemijRodionov added a commit that referenced this issue Nov 22, 2018
Add a fast-test pipeline

Add a check to ensure that each test is tagged. Create a todo to do it properly.

Keep db in fast-test
@0pdd
Copy link
Collaborator

0pdd commented Nov 22, 2018

@artemiy312 the puzzle #358 is still not solved.

@ArtemijRodionov ArtemijRodionov added the report Put it to completed tasks temporary list for business label Nov 22, 2018
@0pdd
Copy link
Collaborator

0pdd commented Nov 26, 2018

@artemiy312 the only puzzle #358 is solved here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2 performer can implement issue at his closest convenient time 30 mins small issues. Usually cosmetic fixes 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

3 participants