Closed Bug 711591 Opened 8 years ago Closed 8 years ago
make the robotium test driver a bit more driver like
some tweaks that tfair and automatedtester had talked about. This is a patch that I need to test with and tweak before asking for review. Feel free to chime in now or then to comment.
(In reply to Joel Maher (:jmaher) from comment #0) > some tweaks that tfair and automatedtester had talked about. > > This is a patch that I need to test with and tweak before asking for review. > Feel free to chime in now or then to comment. I think you forgot the patch...
updated patch with local html files for test, and an added assert class. This should be more compatible for selenium and other test driver syntax models.
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #584437 - Flags: review?
Comment on attachment 584437 [details] [diff] [review] updated tests with an asserts framework as well as general cleanup (1.0) Review of attachment 584437 [details] [diff] [review]: ----------------------------------------------------------------- Not entirely sure who you were requesting review from, but since I'm around, I'll take it. Feel free to ask again if you want someone else's feedback. I think the changes look good. You might want to consider removing the setLogFile api from the driver code so no one gets confused, as I mentioned below. But, as far as I can see, this code looks good r+. ::: mobile/android/base/tests/testAwesomebar.java.in @@ +64,5 @@ > actions = new FennecNativeActions(activity, solo, getInstrumentation()); > driver.setLogFile((String)config.get("logfile")); > + > + asserter = new FennecNativeAssert(); > + asserter.setLogFile((String)config.get("logfile")); Do we need to remove the setLogFile function from the FennecNativeDriver code? I think it would be a good thing to do so that there is only one way to call setLogFile. I'm asking as I don't see that in this patch.
Attachment #584437 - Flags: review? → review+
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/2ea7afaa47a9 - one of the two in that push was hitting "TypeError: Cc['@mozilla.org/android/bridge;1'] is undefined at :0" in desktop mochitest-other.
this actually wasn't backed out (or somehow landed again by accident). I pulled the latest source and my other patch was missing, but this patch (new files and all) were in the tree. I will see if this all makes it to mozilla-central on the next merge.
/me does a quick merge to hide the evidence https://hg.mozilla.org/mozilla-central/rev/632f07583bd8
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla12
Jorl, please request aurora approval or mark the whiteboard not-fennec-11
You need to log in before you can comment on or make changes to this bug.