And another test to show behaviour of run-once interactions on temp objects
affecting real-objects.

And a global search/replace on assertEquals -> assertEqual on
testInteractionWorkflow.py

Only prevent transition from running if it has actually run. If its guard
prevents it from running, consider it still runnable in this transaction.

This change doesn't help to skip the interaction on the real object if it's
not forbidden on the temp one.

Mark as NotImplementedError, as use case is not described yet.

portal_instrospections is been used by SlapOS as a single place for detect
lack of configuration (ie.: Missing bt5s, Missing memcache configuration...)

Move to tnstance creation make things cleaner and it creates a standard
place for information collection.

login.

Otherwise it can't be set, just like variation_category_list

and account's number of failures and stop user (if required) from
logging in.

this should have been part of commit 79a2aaf5

Update Folder.callMethodOnObjectList so that an active proces can collect
results.

Add view and property-sheet for Specialise Divergence Tester so that only specialise links of specific portal types can be divergence tested (or, alternatively excluded from divergence testing).

Use the accessors above to restrict which specialise links are selected for testing on the movement by the Specialise Divergence Tester.

JSON allows to exchange python dictionaries in safe and simple way.

So thanks to using directory where test results are posted, it is possible that call
external tool will call erunTestSuite, which would later attach to such directory
"x" and do "something" more with stored test results.

Now is possible to run these tests under portal_classes due the "magic" done by runLiveTest and also run using runUnitTest.

This can happen, for example, when there is a broken subobject on a
property sheet.
The main advantage of this change is to make the error cause easier to
track down.

Whatever the reason we exit this code, we are not generating this portal
type anymore. So remove it from set.

simulation_movement.setPropertyList(
  'variation_category',
  movement.getProperty('variation_category_list'))

Does work after all. Note the absence of the _list suffix on the setting
property.

If a mapped property had a '-', it would be called like:

document.setProperty('-price', -20.0)

Also, add a warning about trying to set 'variation_category_list' in a
SimulationMovement with property mapping.