Forums

Posting in these forums is disabled. These forums will be available for archive purposes. Please join the new forums at the links below:

  • yui-support - replaces the `YUI 3.x` and `YUI 3 Gallery` forums.
    We have created the following discussion categories within this group to aid discoverability for these most-used topics:
    • Charts for YUI Charts support.
    • DataTable for YUI DataTable support.
    • Gallery for YUI Gallery support, including support for published Gallery components as well as the Gallery process in general.
    • Tools for support of YUI’s suite of developer tools such as selleck, shifter, grover, yogi, etc.
    • Everything Else for questions that don’t fit one of the categories above, we’ve got you covered here.
  • yui-deprecated - replaces the `YUI 2.x` forum and the forums of other deprecated products (`YUI Doc`, `Builder`, `YUI PHP Loader`, etc.).
  [ 4 posts ]
New Topic | Post Reply | Print view
Previous topic | Next topic

Joakim B

  • Username: jockster
  • Joined: Tue Sep 18, 2012 12:08 am
  • Posts: 2
  • Offline
  • Profile
Tags:
  • Continuous integration
  • browser
  • yeti
  • firefox
  • proposal
  • safari

Proposal: Forcing yeti to fail when browsers isnt present

Post Posted: Tue Sep 18, 2012 12:36 am
I would like to propose that one would be able force tests to fail tests, when specific browsers aren't available.

Let's say that I build a javascript application that must work in both Firefox 15 & Safari @ iphone. I have my yeti hub running with an instance of Firefox & Safari connected to the hub.
If the Firefox agent crashes, the tests will still pass as Safari still is connected, but I cannot reassure that my application will work in both environments.

So ultimately, I would like to do something like;

Code:
yeti --hub http://test.yeti.cx/ test/*.html --force-present Firefox15


or
Code:
yeti --hub http://test.yeti.cx/ test/*.html --force-present config.json
as I reckon that specifying several User-agents may be a bit harsh.

Config.json could look mething like:

Code:
{
    forcePresent: ["Firefox (15.0.1) / Linux", "Safari (5.1) / iOS 5.1.1"]
}

Reid Burke

YUI Developer

  • Username: reid
  • Joined: Mon May 11, 2009 1:02 pm
  • Posts: 28
  • Location: Sunnyvale, California
  • Twitter: reid
  • GitHub: reid
  • Gists: reid
  • IRC: reid
  • YUI Developer
  • Offline
  • Profile
Tags:
  • ticket

Re: Proposal: Forcing yeti to fail when browsers isnt presen

Post Posted: Fri Sep 21, 2012 10:04 am
Joakim,

I like your idea. We have an open ticket for running batches with specific agents and I have noted your feedback on that ticket with a link to your post.

I am planning the next week of work on Yeti and will be updating tickets that are selected for that sprint today. Let me know if you have any other feedback and thank for using Yeti!

Reid

Joakim B

  • Username: jockster
  • Joined: Tue Sep 18, 2012 12:08 am
  • Posts: 2
  • Offline
  • Profile

Re: Proposal: Forcing yeti to fail when browsers isnt presen

Post Posted: Tue Nov 20, 2012 7:25 am
Hi again Reid,

Do you have any idea on when this could be implemented?
I would love to help out but yeti just seems a bit too complex for my skills.

Thank you

Joakim

Reid Burke

YUI Developer

  • Username: reid
  • Joined: Mon May 11, 2009 1:02 pm
  • Posts: 28
  • Location: Sunnyvale, California
  • Twitter: reid
  • GitHub: reid
  • Gists: reid
  • IRC: reid
  • YUI Developer
  • Offline
  • Profile
Tags:
  • github
  • ticket

Re: Proposal: Forcing yeti to fail when browsers isnt presen

Post Posted: Tue Nov 20, 2012 1:28 pm
Joakim,

I will likely not get to this ticket until 2013 at the earliest. I apologize for the delay.

To help you understand what my current priorities are, I have published my goals for the next month of Yeti development here:

https://github.com/yui/yeti/wiki/Roadmap

These goals are very ambitious and I need as much time as possible to work on them. The purpose of my focus is to get the YUI Library using Yeti in CI by the end of the year.

Unfortunately, some features that would help the community — like this one — do not fall into the focus of my effort for this quarter. If I do finish these goals ahead of schedule, I will have time to work on this ticket for you. Put yourself on the ticket's Cc to stay updated!

I will publish new goals in Q1 2013. And as always, anyone is welcome to work on any open Yeti ticket by following the Contributor Guidelines.

http://yeti.cx/contribute/

Thanks for understanding and let me know if you have any other questions.

Reid
  [ 4 posts ]
New Topic | Post Reply | Print view
Previous topic | Next topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum