| Page 1 of 1 | [ 4 posts ] |
|
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"] } |
|
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 |
|
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 |
|
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 |
| Page 1 of 1 | [ 4 posts ] |
| 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 |
© 2006-2013 Yahoo! Inc. All rights reserved.
All code on this site is licensed under the BSD License unless stated otherwise.
About This Site · Security Contact Info
Powered by phpBB® Forum Software © phpBB Group