FLUID-6077: Modernise support in IoC Testing framework for "change" type fixtures

Metadata

Source
FLUID-6077
Type
Task
Priority
Major
Status
Open
Resolution
N/A
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2016-11-16T18:56:02.858-0500
Updated
2016-11-16T18:57:14.948-0500
Versions
  1. 2.0
Fixed Versions
N/A
Component
  1. IoC Testing Framework

Description

Our support for issuing changes via the ChangeApplier in the IoC testing framework is rather old-fashioned and has a syntax which dates from before the FLUID-5024/FLUID-5114 model relay rewrite. It still exposes access to the applier's modelChanged event which should really be an implementation detail, as in:

{
                listenerMaker: "fluid.tests.makeChangeChecker",
                makerArgs: ["{asyncTester}.options.furtherTextValue", "textValue"],
                // alternate style for registering listener
                spec: {path: "textValue", priority: "last"},
                changeEvent: "{asyncTest}.applier.modelChanged"
            },

We should normalise this syntax to conform with the standard one for triggering changes in the new(er) declarative framework as per http://docs.fluidproject.org/infusion/development/ChangeApplierAPI.html#declarative-style-for-triggering-a-change