FLUID-5132: IoC testing framework does not accept IoC configuration for test fixtures

Metadata

Source
FLUID-5132
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2013-09-12T04:16:02.580-0400
Updated
2013-10-23T15:45:44.185-0400
Versions
  1. 1.4
Fixed Versions
  1. 1.5
Component
  1. IoC System
  2. Testing Infrastructure

Description

The IoC testing framework's main driver, the function fluid.test.runTests, only accepts a list of bare gradeNames as its specification of the test environments to be run. For example, this driver runs three test environments -

fluid.test.runTests([
"fluid.tests.myTestTree",
"fluid.tests.asyncTestTree",
"fluid.tests.initTree"
]);

This inhibits reuse of testing environments, where these only differ in the content of configuration - KASPAR's current integration testing for GPII is required to illegally fabricate fresh grades in a loop in order to issue different integration testing configurations. We should support a syntax that essentially takes the form of free subcomponents - for example,

fluid.test.runTests([ {
type: "fluid.myTestTree",
options: {
myValue: 3
}
});

Comments