And this would be really nice :
Now I would really love to put some time in this, but before I do that I want to know if there is even a demand for this and if this fits in the philosophy of the Silverstirpe core team.
And of course I might be missing some key aspects in achieving this, or there might be better ways of implementing this.
What do you think?
+1,
though testing with many fixtures is dead slow on mysql. There are some workarounds to use sqlite for testing which speeds up a lot, e.g. http://www.silverstrip.es/blog/how-to-speed-up-unit-tests-using-sqlite/
Maybe we could bundle some stuff as a dev-requirement in a seperate module?
Cheers,
Werner
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
Well, sometimes you want to check the DB after a test has failed.
Some sql statements to delete all test DBs might be fine.
Von: marv...@gmail.com [mailto:silverst...@googlegroups.com] Im Auftrag von Martijn
Gesendet: Donnerstag, 12. Mai 2016 09:39
An: SilverStripe Core Development
--
$
composer global require axyr/silverstripe-cli-installer
You can create a fresh installation anywhere with :
$ silverstripe new projectname
$ composer create-project silverstripe/installer projectname
if you ask me...
If a _ss_environment.php file is present in the directory where from the command is executed, it takes that values as default for the config questions.
I tested it on OSX and Ubuntu, and it works pretty good in the direction I had in mind.
Once all the packages are in cache, you get a new project in seconds WITH a working UnitTest setup.
Please let me know what you think of it!
With one test database that would still be possible. one test database per install that will be cleared before the test runs is fine. not 100 ss_tmpdb12334's
--
I've always wondered ain't this but why not use composer to autoload classes? I know the manifest is needed right now for the lack of namespaces so maybe there's just a lot of work to be done there. Anyway his way you don't need he class manifest in order to get new classes working as classes are discovered very quickly and automatically via simple algorithm. Even if you did need a 'manifest' composer already can generate a class map for you 🤓
--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at https://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
1. php framework/cli-script.php dev/build
2. vendor/bin/phpunit mysite
3. visit my.website.dev
will result in memory exhausted error.