Hi Anjali, On Sun, Mar 6, 2016 at 1:23 PM, Anjali <shally.hp5(a)gmail.com> wrote: As you`ve said you`ve previously used Maven, you need to look a the failure reason details which are presented above the part that you have shown in your screenshots, exactly when they happened during the build. More exactly, you are interested in the stacktrace of the actual failing test and not the summary which says generically that "There were test failures". Even so, I manage to see part of the "WebDriver failed to connect" message which usually means that you have not set up the correct Firefox version to use with the tests, as described in the test documentation section at http://dev.xwiki.org/xwiki/bin/view/Community/Testing#HBrowserversion Not really. However such a detailed analysis could be part of your proposal or even part of the work you commit to do once/if accepted. As mentioned in the reply to your initial mail ( http://markmail.org/message/fk5kqvkpjjn5bldf#query:+page:1+mid:pd6r5b45ccjc…), for functional tests, you would need to focus on moving the existing test from xwiki-enterprise-test-selenium to their specific modules inside xwiki-platform. For unit tests, you can recognize them inside the xwiki-platform repository as being unit tests extending any of "AbstractBridgedXWikiComponentTestCase", "AbstractXWikiComponentTestCase", "AbstractMockingComponentTestCase" or "AbstractComponentTestCase", which are the older component test framework and not using the newer Mockito-based and @Rule-based (e.g. MockitoComponentMockingRule) framework both of which are defined in https://github.com/xwiki/xwiki-commons/tree/master/xwiki-commons-tools/xwik… . Example old unit test: https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… Example migrated unit test: https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi… Most old unit tests are located in the module xwiki-platform-oldcore but there may be others in other modules as well. XWiki has set up a Continuous Integration service based on Jenkins ( https://jenkins-ci.org/ ) which, besides the build, also runs unit and functional tests automatically, for every commit pushed in the source repository. The service is running at http://ci.xwiki.org/ For development, however, you will be running unit or functional tests locally, by running individual tests you are interested in (as detailed in the testing documentation for each test type http://dev.xwiki.org/xwiki/bin/view/Community/Testing). There is a good distribution of unit and functional tests. Functional tests can be run either: * with a test instance manually started beforehand or * with the specific test instance set up by the test itself (recommended) which is configured in the project's pom.xml and is also used when run by the Continuous Integration service. As I`ve explained in the original mail's answer as well and on the proposal's updated description http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Convertallexistingte… , we need both, but it will be up to the student to analyse, estimate and commit to a particular ratio of functional and unit tests that he/she plans to tackle when writing the student application. It is OK to do both but it is also OK to do just one of them, as long as you show us that you have a good understanding of what it involves and that you are able to finish what you sign up for :) Great! Basic suggestion is to run the test on your machine, see what it does and how that fits with the existing code and then start working on how you can make it use the Page Object approach and how the previous scenario can use the page object you end up creating in order to test exactly the same thing/scenario it was testing before. We`re here to help you along the way. Thanks, Eduard