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

[#1753] Rename tests -> tests_legacy. #2221

Merged
merged 7 commits into from
Mar 16, 2015
Merged

Conversation

davidread
Copy link
Contributor

I think we can worry about renaming new_tests to tests once this has been merged, to reduce the chance of "noise between branches" mentioned here: #1753 (comment)

@wardi
Copy link
Contributor

wardi commented Jan 15, 2015

@davidread to prepare for renaming new_tests how about moving to tests/legacy instead of tests_legacy so we don't end up with two test dirs in the top level?

@davidread
Copy link
Contributor Author

Sounds good, i'll give it a try.

@davidread
Copy link
Contributor Author

@amercader you mentioned before you'd be up for renaming tests in CKAN 2.3. I think this PR is pretty straightforward, and the longer it is not merged, the harder it will be to merge, since it affects every legacy test. So can this go in the 2.3 milestone?

Once this is merged I'll do a PR for moving new_tests to tests, and ideally that'd go into the same CKAN release. That would mean that tests in extensions will only need updating once.

…tests

Conflicts:
	ckan/tests/functional/api/base.py
	ckan/tests/legacy/lib/test_datapreview.py
	ckan/tests/legacy/lib/test_munge.py
	ckanext/imageview/tests/test_view.py
	ckanext/pdfview/tests/test_view.py
	ckanext/webpageview/tests/test_view.py
	setup.py
@wardi wardi merged commit 87742eb into master Mar 16, 2015
@davidread davidread deleted the 1753-rename-legacy-tests branch March 16, 2015 14:28
@davidread
Copy link
Contributor Author

Whoop!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants