Show last authors
1 {{box cssClass="floatinginfobox" title="**Contents**"}}
2 {{toc/}}
3 {{/box}}
5 There are various types of tests and everyone has its own terminology. You'll find below the XWiki terminology and best practices related to testing.
7 Check the [[general development flow>>dev:Community.DevelopmentPractices||anchor="HGeneralDevelopmentFlow"]] to understand better how testing fits in the larger picture.
9 = Testing Strategy =
11 Here's the general testing methodology used by the XWiki project:
13 * Code committed must have associated automated tests.
14 * There are [[checks in the build>>Community.Building||anchor="HAutomaticChecks"]] (in the ##quality## profile - executed automatically on the CI) to ensure that committed code:
15 ** do not reduce the total test coverage for that module
16 * Developers run unit and functional tests on their machines daily and frequently.
17 * Unit and functional tests are executed by the CI, at each commit.
18 * Most automated functional tests are currently running in a single environment (HSQLDB/Jetty/Firefox). However, we've started to use Docked-based testing to test automatically using several configurations and are migrating more and more tests to that. There are jobs in XWiki's CI that execute tests in all configurations regularly (not at each commit though but as much as possible).
19 ** Manual tests are also executed at each release by dedicated contributors and they manually execute tests that are not covered by the automated tests.
20 * Performance tests are executed manually several times per year (usually for LTS releases and sometimes for stable releases too).
21 * Responsiveness tests (e.g. verify that XWiki displays fine on a Mobile) are currently executed manually from time to time by dedicated contributors.
22 * Accessibility (WCAG) tests are performed automatically at each commit.
23 * HTML5 validity tests are performed automatically at each commit.
25 = Unit Testing =
27 == Java Unit Testing ==
29 See [[Java Unit Testing>>Community.Testing.JavaUnitTesting.WebHome]]
31 == JavaScript Unit Testing ==
33 * These are **tests that do not rely on the DOM**, written as "behavioral specifications", using the [[Jasmine>>]] test framework. You can find some information how to write such tests on [[the frontend resources>>xwiki:Documentation.DevGuide.FrontendResources.IntegratingJavaScriptLibraries||anchor="HWhatisJasmine3F"]].
34 * In development mode, you can start the test runner process by running {{code}}mvn jasmine:bdd{{/code}} in your command line. This will start a test runner at ##http:~/~/localhost:8234##, that will run all tests in the ##src/test/javascript## directory. Write your tests there and hit refresh to see the results directly in your browser.
35 * For tests that need a DOM, see [[Functional Testing>>||anchor="HFunctionalTesting"]]
37 == Java Rendering Testing ==
39 We have a special framework for making it easy to write Rendering tests, see the [[Rendering Testing Framework>>rendering:Main.Extending||anchor="HAddingTests"]]
41 == XAR Testing ==
43 See [[XAR Unit Testing>>Community.Testing.XARUnitTesting.WebHome]]
45 = Functional Testing =
47 A functional test requires a running XWiki instance.
49 == Functional UI Testing ==
51 We now have 3 frameworks for running GUI tests:
53 * One based on Docker (and using Selenium 3+). This is now the recommended framework to use for new tests.
54 * One based on Selenium2/Webdriver which is now deprecated and shouldn't be used. We encourage committers to port tests written for it to Docker tests. Especially when committers bring modification to the old tests we encourage them to rewrite the tests as new Docker tests.
55 * A last one based on Selenium1 which is also deprecated and shouldn't be used. We encourage committers to port tests written for it to Docker tests. Especially when committers bring modification to the old tests we encourage them to rewrite the tests as new Docker tests.
57 {{id name="HSelenium3-basedFramework"/}}
59 === Docker-based Testing ===
61 This is currently the official way to write UI functional tests.
63 See [[DockerTesting]].
65 === Selenium2-based Framework ===
67 Using:
69 * To debug a test simply start XWiki somewhere and then debug your JUnit tests as a normal JUnit test in your IDE.
70 ** Note that functional test Maven modules will create an XWiki instance in ##target/xwiki## thanks to the execution of the XWiki Packager plugin, so it's simpler to start this XWiki instance when debugging.
71 * In order to debug more easily flickering tests you can simply add the {{{@Intermittent}}} annotation on your test method and it'll be executed 100 times in a row (you can also specify {{{@Intermittent(repetition=N)}}}to repeat it N times). This is achieved thanks to the [[Tempus Fugit>>]] framework that we've integrated.
72 * To run a specific test, pass the ##pattern## property (it's a regex on the test class name) as in: ##mvn install -Dpattern=TestClass#testName## (this will run the ##testName## test from ##TestClass##)
73 ** More details on the usage of the ##pattern## property and examples can be found in the [[documentation of the XWikiExecutorTestMethodFilter class>>]].
74 * To run the tests on your own running instance (instead of letting Maven close your instance and start a fresh one), use ##-Dxwiki.test.verifyRunningXWikiAtStart=true##. It could be useful to verify that you have not broken the tests on your instance before committing your changes.
75 * By default the Firefox browser will be used but if you wish to run with another browser just pass the ##browser## parameter as in:
76 ** Firefox (default): ##-Dbrowser=*firefox##
77 ** Internet Explorer: ##-Dbrowser=*iexplore##
78 ** Chrome: ##-Dbrowser=*chrome##
79 ** PhantomJS: ##-Dbrowser=*phantomjs##
80 * In case of compatibility problem between the version of the browser and the version of Selenium, you can specify which install of firefox to use thanks to ##-Dwebdriver.firefox.bin##. For example, we use to need Firefox 32 in the past, you could install it locally and refer to it with ##-Dwebdriver.firefox.bin="/path/to/your/firefox-32.0"##.
81 * We check for pages that require Programming Rights automatically by bundling a Listener component that listens to the ##ScriptEvaluatingEvent## event and that drops Programming Rights, in an effort to make the tests fail and so that the developer can notice he requires PR and fix that. In some cases where it's necessary, this can be disabled by setting the configuration {{code}}< testProgrammingRights>false</testProgrammingRights>{{/code}} in the configuration of the Package Mojo, and/or by using a System Property to control where the check is performed, e.g. {{code}}<xwikiPropertiesAdditionalProperties>test.prchecker.excludePattern=.*:XWiki\.XWikiPreferences</xwikiPropertiesAdditionalProperties>{{/code}}. {{info}}Since XWiki 9.8RC1{{/info}}
82 * If the ##xwiki.test.startXWiki## system property is set to ##true## then the test itself will start/stop XWiki. If set to ##false## then it's then the responsibility of the build to start/stop XWiki. Useful when starting.stopping XWiki inside a Docker container handled by the Maven build for example. {{info}}Since XWiki 10.0{{/info}}
84 ==== Best practices ====
86 * Tests are located in ##xwiki-platform## inside the module that they are testing. Note that in the past we were putting functional tests in ##[[xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test>>]]## but we have started to move them inside the specific modules they are testing.
87 * Name the tests using ##<prefix>
88 * Use a test suite to ensure that XWiki is started/stopped only once for all tests in the module:(((
89 {{code language="java"}}
90 @RunWith(PageObjectSuite.class)
91 public class AllITs
92 {
93 }
94 {{/code}}
95 )))
96 * Use the ##maven-failsafe-plugin## for functional UI tests:(((
97 {{code language="xml"}}
98 <plugin>
99 <groupId>org.apache.maven.plugins</groupId>
100 <artifactId>maven-failsafe-plugin</artifactId>
101 </plugin>
102 {{/code}}
103 )))
104 * Locate tests in ##src/test/java## (i.e the default maven location for tests)
105 * Tests should be written using the Page Objects Pattern:
106 ** [[Original article from Simon Steward>>]]
107 ** [[Article from Martin Fowler>>]]
108 * (((
109 Since functional tests take a long time to execute (XWiki to start, Browser to start, navigation, etc) it's important to write tests that execute as fast as possible. Here are some tips:* Write scenarios (i.e. write only a few test methods, even only one if you can so that you can have a single fixture) instead of a lot of individual tests as you'd do for unit tests.
110 * (((
111 Use ##getUtil()## to perform quick actions that are not part of what you wish to test (i.e that are part of the test fixture). For example to create a page you need in your fixture, write:(((
112 {{code language="java"}}
113 getUtil().createPage(...);
114 {{/code}}
115 )))instead of
117 (((
118 {{code language="java"}}
119 WikiEditPage wep = new WikiEditPage();
120 wep.switchToEdit(SPACE_NAME, DOC_NAME);
121 wep.setTitle(DOC_TITLE);
122 wep.setContent(CONTENT);
123 ViewPage vp = wep.clickSaveAndView();
124 {{/code}}
125 )))
126 )))
127 * Your Maven module for test may depend on a specific profile (as a best practice, you can use ##integration-tests##). Doing this, it will be built only when specifically asked with ##-Pintegration-tests## (see below for an example of the ##pom.xml##)(((
128 {{code language="xml"}}
129 <profiles>
130 <profile>
131 <id>integration-tests</id>
132 <modules>
133 <module>application-task-test</module>
134 </modules>
135 </profile>
136 </profiles>
137 {{/code}}
138 )))
139 )))
140 * {{warning}}Never, ever, wait on a timer!{{/warning}} Instead wait on elements.
141 * If you need to create, update or delete a page during your tests, use a space name specific to your test scenario with ##getTestClassName()##. For example:(((
142 {{code language="java"}}
143 getUtil().createPage(getTestClassName(), "Page", "Content", "Title");
144 {{/code}}
145 )))
146 * Tests must not depend on one another. In other words, it should be possible to execute tests in any order and running only one test class should work fine.
147 * Tests that need to change existing configuration (e.g. change the default language, set specific rights, etc) must put back the configuration as it was. This is true only in flavor tests or when several functional tests of different domains are executed one after another. However functional tests located in xwiki-platform specific modules are only running the tests for their module and thus it's not important, and saves times, if they don't clean up.
148 * Tests are allowed to create new documents and don't need to remove them at the end of the test.
149 * Stdout/stderr validation errors(((
150 We have a [[check>>Community.Building.WebHome||anchor="HAutomaticChecks"]] that verifies if functional tests output some invalid content to stdout/stderr. If your test contains such errors it'll fail and then you have 3 options:
152 * It's a normal and expected output from the test (for ex the test verifies an error condition and it's expected it will raise a stack trace in the console). In this case add an expectation in the test. For example:(((
153 {{code language="java"}}
154 public class TemplateTest extends AbstractTest
155 {
156 public void wrongTemplate()
157 {
158 ...
159 this.validateConsole.getLogCaptureConfiguration().registerExpected( "Possible break-in attempt!",
160 "Error getting resource [null]");
161 }
162 ...
163 {{/code}}
164 )))
165 * It's a non-expected error. You then have 2 sub-choices:
166 ** Fix the problem (the best and recommended solution!)
167 ** Increase the technical debt by adding an exclude. For example:(((
168 {{code language="java"}}
169 this.validateConsole.getLogCaptureConfiguration().registerExcludes(
170 "java.lang.IllegalStateException: Response is committed");
171 {{/code}}
172 )))
173 )))
175 Examples of functional tests:
177 * {{scm path="xwiki-platform-core/xwiki-platform-activeinstalls/xwiki-platform-activeinstalls-test"}}Active Installs Application Functional Tests{{/scm}}
178 * {{scm path="xwiki-platform-core/xwiki-platform-administration/xwiki-platform-administration-test"}}Administration Application Functional Tests{{/scm}}
179 * {{scm user="xwiki-contrib" project="application-faq"}}FAQ Application Functional Tests{{/scm}}
180 * {{scm path="xwiki-platform-core/xwiki-platform-ircbot/xwiki-platform-ircbot-test"}}IRCBot Application Functional Tests{{/scm}}
181 * {{scm path="xwiki-platform-core/xwiki-platform-linkchecker/xwiki-platform-linkchecker-test"}}Link Checker Application Functional Tests{{/scm}}
182 * {{scm path="xwiki-platform-core/xwiki-platform-panels/xwiki-platform-panels-test"}}Panels Application Functional Tests{{/scm}}
184 === Old Selenium1-based Framework ===
186 * We were using Selenium RC to perform functional tests for GUI. We had created some JUnit extension to easily write Selenium tests in Java.
187 ** Existing tests can be found in ##[[xwiki-enteprise/xwiki-enterprise-test/xwiki-enterprise-test-selenium>>]]##
188 * To run these tests on your local machine go to ##xwiki-enteprise/xwiki-enterprise-test/xwiki-enterprise-test-selenium## and type ##mvn install##.
189 * To run a specific test, pass the ##pattern## property as in: ##mvn install -Dpattern=DeletePageTest## (this will run the ##DeletePageTest## - Note that you don't have to specify the extension). In addition if you wish to execute only a specific method from a Test Case class, you can pass the ##patternMethod## property as in: ##mvn install -Dpattern=DeletePageTest -DpatternMethod=testDeletePageCanDoRedirect##.
190 * To enable debug output from the selenium server start maven with the ##-Ddebug=true## switch and then all messages from the selenium server are saved to: ##xwiki-enteprise/xwiki-enterprise-test/xwiki-enterprise-test-selenium/target/selenium/server.log##.
191 * To debug a functional Selenium test in your favourite Java IDE go in ##xwiki-enteprise/xwiki-enterprise-test/xwiki-enterprise-test-selenium## and run maven with ##-Dmaven.surefire.debug##. Maven will wait till you connect your IDE to the running JVM on port 5005. You can put a breakpoint in your IDE and debug the test.
193 === Browser version ===
195 Currently we only run our functional tests on the ##Firefox## browser.
196 The browser you use for functional tests needs to match the selenium version, otherwise unpredictable results may occur.
198 * The current ##Selenium## version we are using is ##2.44.0##
199 ** (valid for 18.March.2015. Actual version used can be verified [[here>>]] under the ##selenium.version## property)
200 * The ##Firefox## version we use in you continuous integration agents is ##32.0.1##.
201 ** (valid for 18.March.2015. Ask on the [[list>>dev:Community.MailingLists]] or on [[IRC>>dev:Community.IRC]] for the actual used version since it's not publicly verifiable)
202 ** To determine browser compatibility with the Selenium version used, scan [[Selenium's changelog>>]] and look for entries like "* Updating Native events to support Firefox 24, 31, 32 and 33". That shows the supported browser version for the particular Selenium version.
204 If you wish to run tests with the exact configuration as XWiki's [[Continous Integration server>>]] uses, you need to install and use locally the same Firefox version. To do so, you have to:
206 1. [[Download>>]] the corresponding Firefox release
207 1. Unzip it locally
208 1. Use the ##webdriver.firefox.bin## java system property to specify the location of your firefox version
209 11. Depending on how you are starting the functional tests, you`d have to either add the system property in your maven build (surefire plugin configuration) or in your IDE (run configuration)
210 11. Read [[Selenium's FirefoxDriver documentation>>]] for more information and options
212 === Adding a new maven dependency for minimal war ===
214 All our functional testing are linked to the build of a custom instance of XWiki based on the dependencies contained in the pom.xml of the test.
215 However, those dependencies are added to a minimal war that is built using dependencies located on different places dependending if it is a docker test, or an older functional test.
217 So when a new Maven dependency is added for all distributions, it should be declared in three places:
219 * in {{code}}xwiki-platform-minimaldependencies/pom.xml{{/code}}: this will allow the dependency to be retrieved for both docker tests, and for the standard distribution
220 * in {{code}}xwiki-tools-packager-plugin{{/code}}, in both {{code}}pom.xml{{/code}} and {{code}}{{/code}}: those are used for older functional tests.
222 == IDE Support ==
224 Functional tests are JUnit tests like unit tests. Thus you can execute them from within your IDE. However we usually have them enabled only when the 55##integration-tests## and ##docker## Maven profiles>>Community.Building.WebHome||anchor="HUsingProfiles"]] are enabled so make sure to enable these profiles in your IDE.
226 For example with IntelliJ IDEA:
228 {{image reference="intellijideafunctionaltest.png" width="650px"/}}
230 = XHTML, CSS & WCAG Validations =
232 * We are using JUnit to validate that all XWiki pages produce valid XHTML.
233 ** Existing tests can be found in ##enterprise/distribution-test/misc-tests/##
234 * [[WCAG Testing Strategy>>WCAGTesting]]
235 * CSS validation must be verified manually using the [[W3C validator>>]]. See [[XHTML & CSS Coding Style>>XhtmlCssCodeStyle]].
237 = Performance Testing =
239 * These are memory leakage tests, load tests and speed of execution tests.
240 * They are performed manually and in an ad hoc fashion for now. They are executed for some stable versions and for all super stable versions.
241 * See [[Methodology and reports>>test:Performances.WebHome]].
243 See the [[Profiling topic>>Profiling]] for details on how to use a profiler for detecting performance issues.
245 = Manual testing =
247 {{info}}
248 Here's the spirit we'd like to have from the XWiki Manual Testing Team: [[The Black Team>>]].
249 {{/info}}
251 Besides automated testing, ensuring software quality requires that features be tested by actual users (see [[Manual testing>>]]). In order to manage manual testing, a [[test plan>>]] is required.
253 * [[Manual test reports>>test:Main.WebHome]]
254 * [[Manual Test Strategy>>ManualTestStrategy]]
255 * [[Manual Test Reports>>xwiki:TestReports.WebHome]]
257 = Tools Reference =
259 We use the following tools in our automated tests:
261 * [[JUnit>>]]: test framework
262 * [[Mockito>>]]: mocking environment of unit test to isolate it
263 * [[Hamcrest>>]]: extra assertions beyond what JUnit provides
264 * [[GreenMail>>]]: for testing email sending
265 * [[WireMock>>]]: for simulating HTTP connections to remote servers
266 * [[Selenium>>]]: for functional UI test to simulate a user interacting with XWiki
267 * [[TestContainers>>]]: Docker-based functional testing
268 * [[JMeter>>]]: for performance tests
269 * [[Dumbbench>>]]: for manual performance tests
271 = Test Coverage =
273 See the [[TestCoverage]] page.

Get Connected