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

Migrate tests-legacy directory to tests directory #23462

Closed
10 tasks done
Tracked by #21197
Progi1984 opened this issue Mar 1, 2021 · 1 comment · Fixed by PrestaShop/docs#1244
Closed
10 tasks done
Tracked by #21197

Migrate tests-legacy directory to tests directory #23462

Progi1984 opened this issue Mar 1, 2021 · 1 comment · Fixed by PrestaShop/docs#1244
Assignees
Labels
CI/CD Continuous Integration / Continuous Delivery Developer Feature Developer-oriented feature Feature Type: New Feature migration symfony migration project PR available Solution: issue is being addressed TE Category: Tests
Milestone

Comments

@Progi1984
Copy link
Contributor

Progi1984 commented Mar 1, 2021

@hibatallahAouadni hibatallahAouadni added CI/CD Continuous Integration / Continuous Delivery Developer Feature Developer-oriented feature Feature Type: New Feature migration symfony migration project TE Category: Tests Ready Status: Issue is ready to be worked on labels Mar 1, 2021
@matks
Copy link
Contributor

matks commented Mar 1, 2021

Hi @Progi1984 what does it mean "Migrate tests-legacy directory to tests directory" ?

You can find in https://github.com/PrestaShop/PrestaShop/blob/develop/tests-legacy/README.md the reason why we have tests-legacy and tests. We wanted to keep them split. Do you want to merge them? 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Continuous Integration / Continuous Delivery Developer Feature Developer-oriented feature Feature Type: New Feature migration symfony migration project PR available Solution: issue is being addressed TE Category: Tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants