Changes for page Docker-based Testing
Last modified by Vincent Massol on 2024/03/12 17:22
<
>
edited by Vincent Massol
on 2019/05/15 15:28
on 2019/05/15 15:28
edited by Marius Dumitru Florea
on 2019/05/15 16:15
on 2019/05/15 16:15
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. VincentMassol1 +xwiki:XWiki.mflorea - Content
-
... ... @@ -350,6 +350,20 @@ 350 350 351 351 This is achieved by specifying {{code}}@UITest(servletEngine = ServletEngine.EXTERNAL){{/code}} or passing the {{code}}xwiki.test.ui.servletEngine=external{{/code}} system property. 352 352 353 +A common use case is to debug a failing test. Here's what you can do: 354 + 355 +{{code language="none"}} 356 +## Run the test once to see if it fails and to generate the XWiki instance. This may take some time. 357 +> mvn clean install -Dtest=NavigationPanelIT 358 +## Open a new console, look for the generated XWiki instance inside the target folder and start it. 359 +../target/../jetty > start_xwiki.sh 360 +## Modify the test as needed then go back to the initial console and compile the tests. 361 +## Note that you may also need to build the page objects module if you change those too. 362 +> mvn compiler:testCompile 363 +## Then run the test again to see the changes. This should be way faster than the initial test run. 364 +> mvn surefire:test -Dxwiki.test.ui.servletEngine=external -Dtest=NavigationPanelIT 365 +{{/code}} 366 + 353 353 = Architecture = 354 354 355 355 {{image reference="xwiki-testcontainers.png"/}}