| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
And some little mistakes
|
| |
|
|
|
|
| |
For a not-clear reason, I can't properly drop the current database. Even if Doctrine made a special case for that (https://github.com/doctrine/dbal/pull/849).
So instead of trying crazy things to achieve the test, better way is to skip test (too much wasted days ..)
|
| |
|
|
|
|
| |
It will slow down the whole test suite (because it'll use doctrine command).
Remove unecessary `KernelTestCase`.
Also rename `AbstractControllerTest` to `WallabagApiTestCase` for consistency.
|
| |
|
|
| |
This is not the same message exception from MySQL & SQLite with Postgres.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Ensure that created use during install command will always be unique.
We assume that the install command must be run to initialize a wallabag instance. NEVER to add more user.
Also, use a better way to retrieve the real name of the database and not the one defined in parameters.yml (which isn't the same for test envi because the dbname isn't defined in parameters.yml but directly in config_test.yml)
|
| | |
|
| | |
|
| |
|
|
| |
Will fix #799
|
| |
|
|
| |
will fix #1000
|
| | |
|
| |
|
|
|
|
| |
Also add fixtures for Config
InstallCommand now check if database, schema are here and ask the user what to do (keep or trash & re-create)
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
Instead of the legacy bin/install here is a symfony command that can initialize wallabag.
There are still work to do on the requirements part (to be sure that wallabag can run like a charm).
I've also added (but commented) the fixtures load part (which will need an extra doctrine package). We'll see that point later.
|
