Start large refactoring of tests and project structure
* Put tests in tests/ diretory * Write functional tests * Create setup.py * Put sources into django_migration_linter folder (for future PyPi publishing)
This commit is contained in:
1 parent
6b1bba6326
commit
1cd36825c1
31 files changed
+408
-11
No files matched your search
@@ -19,7 +19,7 @@ Detect backward incompatible migrations for your django project.
|
||||
|
||||
Needed software (in PATH):
|
||||
|
||||
* `python` (only tested on python2.7 (yet))
|
||||
* `python`
|
||||
* `git`
|
||||
* UNIX command line tools like `tail`
|
||||
|
||||
@@ -27,12 +27,6 @@ The linter will try to detect if the project is a django project and is versione
|
||||
|
||||
## Tests
|
||||
|
||||
Launch the tests with: `python -m unittest test_migration_linter`
|
||||
The easiest way to run the tests is to invoke [py.test](https://docs.pytest.org/en/latest/).
|
||||
|
||||
More test are to be written.
|
||||
|
||||
## Improvements
|
||||
|
||||
* More tests (always!)
|
||||
* Detect data migration (not only scheme migrations)
|
||||
* Detection dependent on specified database (mysql, postgresql, ...)
|
||||
More tests are always welcome.
|
||||
Reference in new issue
Block a user