| # |
Jul 5th 2017, 23:09 |
 jeremyharris |
you can pass the name of your template file to FormHelper on create and it will merge them in |
| # |
Jul 5th 2017, 23:08 |
jeremyharris |
yep you’re on the right track |
| # |
Jul 5th 2017, 23:08 |
jarard01 |
I have a template that I need to use in severla places |
| # |
Jul 5th 2017, 23:08 |
jeremyharris |
templates are not loaded into Configure |
| # |
Jul 5th 2017, 23:08 |
jeremyharris |
see: https://book.cakephp.org/3.0/en/views/helpers/form.html#customizing-the-templates-formhelper-uses |
| # |
Jul 5th 2017, 23:07 |
jarard01 |
but it shouldn't be null should it? |
| # |
Jul 5th 2017, 23:07 |
jeremyharris |
that’s not quite how they work, you load them up into the form helper |
| # |
Jul 5th 2017, 23:07 |
jarard01 |
but it returns NULL |
| # |
Jul 5th 2017, 23:07 |
jarard01 |
then I debug: $this->set('form_templates', Configure::read('Templates')); |
| # |
Jul 5th 2017, 23:07 |
jarard01 |
in my controller: use Cake\Core\Configure; |
| # |
Jul 5th 2017, 23:06 |
jarard01 |
I set my template in that file |
| # |
Jul 5th 2017, 23:06 |
jeremyharris |
that particular one doesn’t ship with cake, if that’s what you’re wondering |
| # |
Jul 5th 2017, 23:06 |
jeremyharris |
jarard01 form templates are stored in config, yes |
| # |
Jul 5th 2017, 23:06 |
jeremyharris |
that’s good to hear. too many clients want corners cut when it comes to testing |
| # |
Jul 5th 2017, 23:06 |
urowe |
So we're writing tests and stuff |
| # |
Jul 5th 2017, 23:06 |
urowe |
Yeah, I got this new project, the client is very invested in doing it the right way |
| # |
Jul 5th 2017, 23:06 |
jarard01 |
is this standard cake: config/templatesConfig.php |
| # |
Jul 5th 2017, 23:05 |
jeremyharris |
happy testing :tada: |
| # |
Jul 5th 2017, 23:05 |
urowe |
Thanks a lot! |
| # |
Jul 5th 2017, 23:05 |
urowe |
You saved the day my friend |
| # |
Jul 5th 2017, 23:04 |
jeremyharris |
it’s one of my plugins that has tests with fixtures, pretty small so it’s easy to understand |
| # |
Jul 5th 2017, 23:04 |
jeremyharris |
np, take a look at this: https://github.com/jeremyharris/cakephp-lazyload/tree/master/tests |
| # |
Jul 5th 2017, 23:04 |
urowe |
Thanks |
| # |
Jul 5th 2017, 23:04 |
jeremyharris |
indeed! and since they are dropped and re-created on each test case, you always know what state your DB is in at the start of each test |
| # |
Jul 5th 2017, 23:04 |
urowe |
I hand't really understood how they worked |
| # |
Jul 5th 2017, 23:03 |
urowe |
Oh that's very cool |
| # |
Jul 5th 2017, 23:03 |
jeremyharris |
so you would need a UsersFixture and a RolesFixture. Whatever records exist in those fixtures would be loaded on each test case. Then you can call your app code that does the check, and it will read from the test database (now populated with those records) |
| # |
Jul 5th 2017, 23:02 |
urowe |
In case let's say I want to verify a user has a role that already exists in the database |
| # |
Jul 5th 2017, 23:02 |
jeremyharris |
the fixtures in cakephp set up your database state on each test method, that’s all |
| # |
Jul 5th 2017, 23:02 |
jeremyharris |
you can use a test method with a dataProvider side by side with fixtures - they work fine together |
| # |
Jul 5th 2017, 23:01 |
urowe |
Oh, so I can have some fixed values, let's say roles and have tests to run with dataProvider methods for users? |
| # |
Jul 5th 2017, 23:01 |
jeremyharris |
if you’re familiar with database testing in vanilla phpunit, it’s similar to that process: https://phpunit.de/manual/current/en/database.html |
| # |
Jul 5th 2017, 22:59 |
jeremyharris |
before each test method is run |
| # |
Jul 5th 2017, 22:58 |
jeremyharris |
yep |
| # |
Jul 5th 2017, 22:58 |
urowe |
Let me see if I understand this, fixtures are loaded to the test database before tests are run? |
| # |
Jul 5th 2017, 22:58 |
jeremyharris |
the table will fetch from the test database rather than the live one, assuming you have it configured correctly and your test bootstrap is correct (ships with cakephp/app) |
| # |
Jul 5th 2017, 22:57 |
jeremyharris |
if you want to get a user from the fixture during a test case, simply use TableRegistry::get(‘Users’)->get($userId) |
| # |
Jul 5th 2017, 22:57 |
urowe |
Aren't they redundant ? |
| # |
Jul 5th 2017, 22:57 |
jeremyharris |
I’m not sure what you mean. dataProvider and fixtures are two different things. |
| # |
Jul 5th 2017, 22:57 |
urowe |
Is there any way to stop the call from where it happens and have these records from a dataProvider method? |
| # |
Jul 5th 2017, 22:56 |
jeremyharris |
for example, if you have UsersFixture that has some test user records in it. and you delete a user in a test case, on the next test case, the user would exist again — you have a fresh database to test with. this allows you to write predictable tests against the database because you always know what the database will look like (fixtures) on each test case |