sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-3784) Convert majority of eclipse-based tests to test vlt commands or the ResourceChangeCommandFactory
Date Mon, 26 Feb 2018 21:07:02 GMT

     [ https://issues.apache.org/jira/browse/SLING-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Munteanu updated SLING-3784:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.2)
                   Sling Eclipse IDE 1.2.4

> Convert majority of eclipse-based tests to test vlt commands or the ResourceChangeCommandFactory
> ------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3784
>                 URL: https://issues.apache.org/jira/browse/SLING-3784
>             Project: Sling
>          Issue Type: Test
>          Components: IDE, Testing
>    Affects Versions: Sling Eclipse IDE 1.0.2
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>
> The current mechanism for content sync is
> * for reach resource change/build event/manual publish
> * {{SlingContentModuleFactory}} generates lists of module resources
> * Eclipse change detection mechanism generates a diff
> * {{SlingLaunchpadBehaviour}}  invokes the {{ResourceChangeCommandFactory}} to build
vlt commands
> * vlt commands are executed
> The current eclipse-based tests, while useful, exercise the whole process and are therefore
more brittle and more difficult to write that the alternatives testing a smaller part of the
stack
> We now have tests in place for each of the steps ( excluding of course Eclipse diff generation,
but that's out of scope ). Moving the tests to simpler fixtures will make the tests more stable,
faster and easier to write. 
> We should still keep some end-to-end tests, but we will not aim to test all scenarios
end-to-end.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message