Take the 2-minute tour ×
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It's 100% free, no registration required.

I'm trying out Selenium Builder as an alternative to Selenium IDE and Selenium Webdriver.

I've been pointed to a useful tutorial here: http://sebuilder.github.io/se-builder/

...but this uses Travis as an example and I want to use a local instance of Jenkins.

I'm having trouble configuring Jenkins to run my Selenium Builder Json tests and I'm finding that the console output does not provide the same level of detail as I am used to when running my webdriver tests that Maven takes care of.

The current message is "Build step 'Invoke Selenium Builder script' marked build as failure"

My setup currently is:

Global:
Jenkins 1.567
GitHub Web Hook (not sure what this should be??)

Plugins: 
Selenium Builder 1.11
Github 1.8

My Build:
Source Code: GitHub 
Build trigger: when change pushed to Git
Selenium Builder options: **/seleniumBuilderPOC/tests/loginCheckDrawers.json (not clear correct filepath format??)

Clearly I have some missing elements or mis-configured items - any help much appreciated.

share|improve this question
    
Steerpike - you would have to provide more information from the console output of your test. It is quite likely that you can see where something actually failed (a stacktrace or the like) before Jenkins reported the failure. –  Paul Becotte Jun 11 at 23:11

1 Answer 1

I wrote an example project that uses Java and runs your tests on SauceLabs. It is executed using Maven and so it is perfectly compatible with Jenkins.

share|improve this answer
    
thanks, looks like I can adapt your framework. I'd like to use a local selenium instance/driver rather than Saucelabs. I'm just a little confused how I configure this, i.e. presumably I need the se-builder interpreter to 'run' the builder .json files. So, what I want to do is, build a suite of tests using se-builder plugin, push them to GitHub and have Jenkins run the tests triggered by the push. So, all builder scripts will live in the cloud. Maybe this is over simplistic –  Steerpike Jun 12 at 19:20
    
Sorry, I'm not being very clear. My ideal is that we can keep the tests in .json format and still run them in CI; reason being is lack of technical expertise within team for maintaining java tests –  Steerpike Jun 12 at 19:36

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.