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

create_fixtures.py:80: Use fixtures in every test. #237

Open
0pdd opened this issue Dec 27, 2018 · 0 comments
Open

create_fixtures.py:80: Use fixtures in every test. #237

0pdd opened this issue Dec 27, 2018 · 0 comments
Labels
2 hours some big and monolith issues. For example with hard decisions or discussions 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Dec 27, 2018

The puzzle 230-edd9709f from #230 has to be resolved:

# @todo #230:120m Use fixtures in every test.

The puzzle was created by duker33 on 27-Dec-18.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

0pdd referenced this issue Dec 27, 2018
* rf#230  Refactor const name. CustomPage.ROUTE is the new one

* #229  Test if order send mails

* #230  Add missed custom pages. Create pdd tasks to use test_db at every refarm test

* #230  Cancel fixtures using for orders. Apply review comments
@duker33 duker33 added 2 hours some big and monolith issues. For example with hard decisions or discussions 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it labels Dec 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 hours some big and monolith issues. For example with hard decisions or discussions 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it
Projects
None yet
Development

No branches or pull requests

2 participants