-
Type: Improvement
-
Status: Resolved
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 6.0-HF32, 7.10-HF17, 8.3
-
Component/s: Tests
-
Sprint:nxProduct-W10, nxProduct-W12
Context
Studio bundles are hard to deploy; their requires are not deterministic as they depends of what feature is used. And, as the generated component is containing "user contributions", and the needs to deploy UI stuff comes quickly... it is always very hard to deploy a Studio Bundle in an Unit test.
Proposal
Idea is to partially deploy a bundle, without takings care of all his requirements and all contributions. We should create a new annotation that describes a set of targets to be deployed.
For instance:
@PartialDeploy(bundle = "studio.extensions.project1-myproject", features = { TargetExtensions.Automation.class })
Target Extensions
ContentModel
Contains:
"org.nuxeo.ecm.core.schema.TypeService", "schema"
"org.nuxeo.ecm.core.schema.TypeService", "doctype"
"org.nuxeo.ecm.core.lifecycle.LifeCycleService", "types"
"org.nuxeo.ecm.core.lifecycle.LifeCycleService", "lifecycle"
"org.nuxeo.ecm.directory.sql.SQLDirectoryFactory", "directories"
"org.nuxeo.ecm.core.versioning.VersioningService", "versioningRules"
Automation
Contains:
"org.nuxeo.ecm.core.operation.OperationServiceComponent", "event-handlers"
"org.nuxeo.ecm.core.operation.OperationServiceComponent", "chains"
"org.nuxeo.automation.scripting.internals.AutomationScriptingComponent", "operation"
Custom
Create a new class extending org.nuxeo.runtime.test.runner.TargetExtensions which can inherit from any other TargetExtension (and call the super method)
And in the initialize method; add any "target" you need
- depends on
-
NXDOC-1201 Add troubleshooting information about Studio bundle unit-testing
- Open
- is related to
-
NXP-24593 Cannot use Notification templates from Studio in a Unit test
- Resolved
-
NXDOC-1152 Add Studio Unit Testing page
- Resolved