aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/Wallabag/CoreBundle/Tests/Command
Commit message (Collapse)AuthorAgeFilesLines
* manage assets through npmThomas Citharel2016-06-091-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | first draft remote assetic totally work nearly there use at least nodejs > 0.12 use proper version of grunt bump nodejs version for travis update npm workaround for materialize install node 5.0 add grunt-cli baggy theme & cache node modules cache bower & npm make travis build assets on php7 only exclude installing node & npm if not needed & use bash clean & try to make icomoon work on baggy ready config for travis rebase make travis work more travis work impove travis & update deps add missing pixrem deps add module through oddly lost ui updates install latest nodejs add install_dev.sh, link local binaries for npm/bower/grunt ui improvements (mostly baggy) fix travis build no need to install on travis Add unread filter to entries pages Add the ability to filter for unread pages in the filters menu. Add unread filter test to EntryControllerTest Add a new test to the EntryControllerTest collection which checks that only entries which have not been archived (and are treated as "unread") are retrieved. Improve English translation Update FAQ -Fix grammar -Add notes about MTA, firewall, and SELinux Update installation instructions -Fix grammar -Add SELinux section add screenshots of android docu in English Fix the deletion of Tags/Entries relation when delete an entry Fix #2121 Move fixtures to the right place Display a message when saving an entry failed When saving an entry fail because of database error we previously just returned `false`. Now we got an error in the log and the displayed notice to the user is updated too. Change ManyToMany between entry & tag Following https://gist.github.com/Ocramius/3121916 Be sure to remove the related entity when removing an entity. Let say you have Entry -> EntryTag -> Tag. If you remove the entry: - before that commit, the EntryTag will stay (at least using SQLite). - with that commit, the related entity is removed Prepare wallabag 2.0.5 enforce older materialize version
* Convert array + phpDocJeremy Benoist2016-04-122-26/+26
| | | | Thanks for https://github.com/thomasbachem/php-short-array-syntax-converter
* Move setup config outside setupAdminJeremy Benoist2016-04-111-24/+30
| | | | If user doesn't want to create a new admin (even if it's recommended) the internal config weren't created resulting in error when using the interface.
* Skipping all Posgres test for wallabag:installJeremy Benoist2016-02-291-20/+18
| | | | | | | | | | | | | | We already faced this problem but we are facing it again. https://github.com/wallabag/wallabag/commit/d502762598db68ec822078642df8f6a8214202f7 It seems we can drop a database properly using wallabag:install. The server log keep saying: ERROR: source database "template1" is being accessed by other users DETAIL: There is 1 other session using the database. STATEMENT: CREATE DATABASE "wallabag_test" Which means, it can't remove the database wallabag_test because one other person is using it.
* Fix testsJeremy Benoist2016-01-311-0/+1
|
* Add tests on TagAllCommandJeremy Benoist2016-01-211-0/+60
| | | | Some simple tests
* Symfony Upgrade Fixer FTWJeremy Benoist2016-01-151-6/+6
| | | | symfony-upgrade-fixer fix src/Wallabag/
* Remove duplicate commentsJeremy Benoist2015-11-071-7/+1
|
* CSJeremy Benoist2015-11-071-4/+4
|
* Skipping PostgreSQL test that drop databaseJeremy Benoist2015-11-071-29/+40
| | | | | | 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 ..)
* Fix deprecated helper in commandJeremy Benoist2015-11-061-42/+30
|
* Fix testsJeremy Benoist2015-09-121-4/+4
| | | | | | | 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)
* implement FosUserNicolas LÅ“uillet2015-09-111-1/+1
|
* Move API stuff in ApiBundleJeremy2015-04-011-2/+2
|
* Update InstallCommand testJeremy2015-03-311-4/+11
| | | | | | | | They are god damn too long to execute because it launch external command (mostly related to doctrine). So I've added a PHPUnit @group (`command-doctrine`) so that we can avoid launching them on a regular basis, like that: `phpunit --exclude-group command-doctrine`
* More tests on the install commandJeremy2015-02-221-3/+216
|
* sqlite doesn't support getListDatabasesSQLJeremy2015-02-221-1/+1
|
* Improve install command & add testJeremy2015-02-221-0/+61
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)