Behat: New fixture Given the"block" exists:
Bug #1437956 reported by
Jinelle Foley-Barnes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Hi,
It would be more efficient if we had a fixture for just adding blocks to a portfolio.
As an example the fixture could say:
And the given "name of block" block exists:
We could also make this fixture link to a group/institution. So the following blocks exists for a certain group page. Don't know if that's plausible or is right, but it's an idea.
Thanks ,
Jinelle
Changed in mahara: | |
milestone: | 15.10.0 → 16.04.0 |
status: | New → Confirmed |
Changed in mahara: | |
milestone: | 16.04.0 → 16.10.0 |
Changed in mahara: | |
milestone: | 16.10.0 → 16.10.1 |
Changed in mahara: | |
milestone: | 16.10.1 → 17.04.0 |
Changed in mahara: | |
milestone: | 17.04.0 → none |
To post a comment you must log in.
This would be a bit more complicated that the other create _* functions in TestingDataGene rator.php as they have a predefined set of values that can be used (and unlikely to change much over time)
But blocks tend to be plugins with their own sets of config fields/values and some rely on certain artefacts existing, eg Journal entry block needs a blogpost artefact.
So we'd need to work out:
1) what the minimum bits of information we'd need that is generic to every block.
2) how to handle the custom fields of every block - and what values to set them to by default.
3) do we need to also generate specific underlying artefacts? and if so how to handle creating those