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

test_views.py:14-16: Remove hardcoded fixture data.... #154

Open
0pdd opened this issue Jul 23, 2018 · 0 comments
Open

test_views.py:14-16: Remove hardcoded fixture data.... #154

0pdd opened this issue Jul 23, 2018 · 0 comments
Labels
3 we can defer this issue. But it'll good to implement it 30 mins small issues. Usually cosmetic fixes cleanup everything that do project stronger, flexible, reusable easy new teammates can start with such issues to become familiar with project take it any teammate can take this issue and start working with it

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jul 23, 2018

The puzzle 360-25169cf6 from #360 has to be resolved:

# @todo #360:30m Remove hardcoded fixture data.
# Replace `url_from` and `url_to` with urls, generated from db.
# It'll be much more short and clear.

The puzzle was created by duker33 on 23-Jul-18.

Estimate: 30 minutes,

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 Jul 23, 2018
* stb#250  Create initial tests for refarm_redirects app

* stb#250  Review#1 minor fixes. Change loop redirects test condition
@duker33 duker33 assigned duker33 and unassigned duker33 Jul 23, 2018
@duker33 duker33 added 30 mins small issues. Usually cosmetic fixes 3 we can defer this issue. But it'll good to implement it easy new teammates can start with such issues to become familiar with project cleanup everything that do project stronger, flexible, reusable take it any teammate can take this issue and start working with it labels Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 we can defer this issue. But it'll good to implement it 30 mins small issues. Usually cosmetic fixes cleanup everything that do project stronger, flexible, reusable easy new teammates can start with such issues to become familiar with project take it any teammate can take this issue and start working with it
Projects
None yet
Development

No branches or pull requests

2 participants