On Tue, Aug 7, 2012 at 4:33 AM, sasinda rukshan <[email protected]> wrote: > Hi Thomas, >>>I restarted it and it seems ok now. > Thanks a lot. > Instrumentation tests that check the activities are running ok. > (XWiki Android Instrumentation > Tests<http://ci.xwiki.org/job/xwiki-android-client/216/org.xwiki.android$xwiki-android-tests-instrumentation/> > ) > > I disabled the base rest api tests (xwiki-android-test-rest). I'll enable > them in the next commit. > There should be a local xwiki test instance in jenkins server as well. Can > you tell me how to access it.
Actually there is none. What we do is that in all the tests that needs an instance of XWiki we start XWiki before and stop it after (before and after the whole test suite not for each test otherwise it would way too slow) to be sure to have a clean instance of XWiki every time and to not require anything in order to execute the test (for example you can build the whole XE with test anywhere as long as you have maven and Firefox installed). In "desktop" integration test what is taking care of starting and stopping XE instance from the tests is https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-test/src/main/java/org/xwiki/test/integration/XWikiExecutor.java through https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-test/src/main/java/org/xwiki/test/integration/XWikiExecutorSuite.java. > Tried http://ci.xwiki.org:8080. Since the test properties are directing to > a local server instance 10.0.2.2:8080 it should be there. > > We will be running tests bottom up. i.e. low lvl rest API --> Rest API in > RAL --> application layer UI components. And RAL tests will use low lvl > rest API to achieve its pre-conditions and do cleanup after tests. If low > level fails testing highlvl ones are not meaningful if they depend on the > components that failed. ;-). > > Best Regards. > Sasinda. > > > >> >> >> On Mon, Aug 6, 2012 at 1:00 PM, Thomas Mortagne <[email protected] >> > wrote: >> >>> On Mon, Aug 6, 2012 at 9:12 AM, Thomas Mortagne >>> <[email protected]> wrote: >>> > On Mon, Aug 6, 2012 at 9:10 AM, Thomas Mortagne >>> > <[email protected]> wrote: >>> >> On Mon, Aug 6, 2012 at 8:57 AM, Thomas Mortagne >>> >> <[email protected]> wrote: >>> >>> On Sun, Aug 5, 2012 at 5:42 PM, sasinda rukshan >>> >>> <[email protected]> wrote: >>> >>>> Hi Thomas, >>> >>>> :-) >>> >>>> Also still we cannot ignore failed tests in maven android plugin. If >>> a test >>> >>>> fails we get Build Failure as result. >>> >>> >>> >>> Well that's the whole point, not sure why you want to ignore failing >>> tests. >>> >>> >>> >>>> http://code.google.com/p/robotium/issues/detail?id=130 >>> >>>> >>> >>>>> Need an AVD / Device connected to Jenkins to >>> >>>> run the tests. >>> >>>> I think you just have to download android sdk to the jenkins server >>> and use >>> >>>> avd-manager to start up an avd in it. >>> >>>> Not urgent ;-). >>> >> >>> >> Well thing is there is an AVD running and always have (since it was >>> >> required by previous tests) so I don't understand exactly what's >>> >> wrong. >>> > >>> > Here is what I have in ps aux: >>> > >>> > emulator -avd test-2.1 -noaudio -no-window -wipe-data >>> >>> Looks like it was not in a very good state actually, I restarted it >>> and it seems ok now. >>> >>> > >>> >> >>> >>>> >>> >>>> Still writing tests for core module. >>> >>>> >>> >>>> Regards. >>> >>>> Sasinda Rukshan. >>> >>>> >>> >>>> On Sun, Aug 5, 2012 at 8:49 PM, Thomas Mortagne < >>> [email protected]> >>> >>>> wrote: >>> >>>>> >>> >>>>> On Sun, Aug 5, 2012 at 4:46 PM, sasinda rukshan >>> >>>>> <[email protected]> wrote: >>> >>>>> > Hi Thomas, >>> >>>>> > Thnx. >>> >>>>> > >>> >>>>> >>No, you need to start one (which is not very hard with >>> jetty/hsqldb >>> >>>>> >>distribution) >>> >>>>> > Well what about the earlier project's test server. It should have >>> had >>> >>>>> > its >>> >>>>> > test environment setup properly. Shouldn't it?. >>> >>>>> >>> >>>>> Yes it should have but Chamika did not had time to finish. >>> >>>>> >>> >>>>> > >>> >>>>> > >>> >>>>> >>(but then you have the risk that you don't >>> >>>>> >>have the exact same behavior) when you start the tests. You can >>> look >>> >>>>> >>at how >>> >>>>> >> >>> >>>>> >> >>> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test/xwiki-enterprise-test-rest >>> >>>>> >>does it for example. >>> >>>>> > Thanks. I'll make the setup, tear down methods to achieve >>> preconditions >>> >>>>> > and >>> >>>>> > cleanup. >>> >>>>> > >>> >>>>> > Best Regards. >>> >>>>> > >>> >>>>> > On Sun, Aug 5, 2012 at 7:14 PM, Thomas Mortagne >>> >>>>> > <[email protected]> >>> >>>>> > wrote: >>> >>>>> >> >>> >>>>> >> On Sun, Aug 5, 2012 at 11:42 AM, sasinda rukshan >>> >>>>> >> <[email protected]> wrote: >>> >>>>> >> > Hi Thomas, >>> >>>>> >> > >>> >>>>> >> > >>> >>>>> >> > This is the latest result for >>> xwiki-android-tests-instrumentation >>> >>>>> >> > (The >>> >>>>> >> > UI stress testing test module) >>> >>>>> >> > >>> >>>>> >> > >>> >>>>> >> > >>> >>>>> >> > [INFO] *Found 0 devices connected with the Android Debug >>> Bridge* >>> >>>>> >> > mojoFailed >>> >>>>> >> > >>> >>>>> >> > >>> com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.3.0(default-internal-pre-integration-test) >>> >>>>> >> > projectFailed >>> >>>>> >> > >>> org.xwiki.android:xwiki-android-tests-instrumentation:1.0-SNAPSHOT >>> >>>>> >> > sessionEnded >>> >>>>> >> > >>> >>>>> >> > >>> >>>>> >> > Need an AVD / Device connected to Jenkins to run the tests. >>> >>>>> >> >>> >>>>> >> Will look at it. >>> >>>>> >> >>> >>>>> >> > >>> >>>>> >> > Also the ....test-rest will have failures if some >>> preconditions are >>> >>>>> >> > not >>> >>>>> >> > met. (like having a page named Blog/test2 ) >>> >>>>> >> > >>> >>>>> >> > Is there a testing server instance running on the Jenkins >>> server?. >>> >>>>> >> >>> >>>>> >> No, you need to start one (which is not very hard with >>> jetty/hsqldb >>> >>>>> >> distribution) or mock one (but then you have the risk that you >>> don't >>> >>>>> >> have the exact same behavior) when you start the tests. You can >>> look >>> >>>>> >> at how >>> >>>>> >> >>> >>>>> >> >>> https://github.com/xwiki/xwiki-enterprise/tree/master/xwiki-enterprise-test/xwiki-enterprise-test-rest >>> >>>>> >> does it for example. >>> >> > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
