mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

This would be a bit more complicated that the other create _* functions
in TestingDataGenerator.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

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1437956

Title:
  Behat: New fixture Given  the"block" exists:

Status in Mahara:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1437956/+subscriptions