Yes, please! As part of this process, would we change things such that you don't need to build build/mobile/robocop when making changes to test files? If so, that would make building test changes much more intuitive.
Not to derail this thread (although I guess I'm doing it anyway), but I've also wondered if we should make a Firefox for Android::Testing bugzilla component to make it easier to track changes to our test framework, as well as bugs with the tests themselves (e.g. the plethora of intermittent oranges). Margaret On Thu, Nov 14, 2013 at 11:56 AM, Nick Alexander <[email protected]>wrote: > On 13-11-14 11:16 AM, Lucas Rocha wrote: > >> Sounds like a good plan. >> >> Just wondering: what kind of sibling folder would sit beside this >> 'browser' directory in 'mobile/android/tests/browser/robocop'? In other >> words, why not 'mobile/android/tests/robocop' instead? >> > > Great question. mobile/android/tests/browser/junit3! And maybe /junit4! > So browser is a sibling to background, and within we have specific test > suites. It's possible we make an Espresso test suite, etc, etc. > > Nick > > > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
