=== nik90_ is now known as nik90 === dkessel_ is now known as dkessel [13:50] Hi, I have a problem with ubuntuuitoolkit and the AppHeader proxy [13:51] with "_get_action_button_in_overflow()" in particular [13:52] sometimes the action is clicked, without a visible overlay [13:52] which happens here: http://91.189.93.70:8080/job/generic-mediumtests-utopic-weather-app/lastSuccessfulBuild/artifact/ubuntu_weather_app.tests.test_settings.TestSettings.test_switch_wind_scale%20%28with%20mouse%29.ogv === om26er is now known as om26er|dinner [16:01] I was looking at: http://unity.ubuntu.com/autopilot/tutorial/good_tests.html#scenarios...is there a way to specify that the scenarios are only used on some of the tests in the class? My understanding is that each test is run once for each scenario in the list. Is there a way to override that, or do tests that use scenarios and tests that don't alwa [16:01] ys have to be in separate classes? [16:01] I was hoping barry would be around, but he's not.. Might be difficult to get an answer today.. holidays :-) [16:02] ok. I can always ask again later, nbd. [16:04] https://pypi.python.org/pypi/testscenarios/ === elopio_ is now known as elopio === om26er|dinner is now known as om26er [17:38] gerlowskija, offhand, I don't know of a nice way to selectively apply scenarios within a class. But that smells to me like your TestCase classes are too big... generally you'd only group very similar tests into a class. [17:41] in that same guide, see 'Test One Thing Only', and 'Test Length' :) [17:41] gerlowskija, that's a good document btw.. I forgot that was part of AP docs [19:22] cgoldberg: haha fair enough. I'm not against splitting classes, just wanted to make sure there wasn't some other best-practice I was missing. Thanks for weighing in; I'll split the classes === lderan_ is now known as lderan