Get chrome tests running on Mac OS
googlecodemigrator opened this issue · 14 comments
From dam...@gmail.com on November 26, 2012 10:11:55
We need to make sure these tests are also runnable on Mac OS
Original issue: http://code.google.com/p/teammatespes/issues/detail?id=393
From dam...@gmail.com on November 27, 2012 06:38:34
Labels: Type-Task
From dam...@gmail.com on February 20, 2013 02:21:58
Labels: Priority-Low
From eugenehu...@gmail.com on March 06, 2013 09:58:17
Hi Damith, can i take this issue?
From dam...@gmail.com on March 06, 2013 15:20:59
Sure Eugene, you can give it a try :-). Since you've done enough already, doing this one is not a must.
Owner: eugenehu...@gmail.com
Labels: Difficulty-High
From eugenehu...@gmail.com on March 11, 2013 04:10:20
Support for chrome added. https://code.google.com/r/eugenehuang87-teammates/source/detail?r=cdf33cc404ef60e5a23d2964abb0b07b1e2cfa9b&name=Issue393 Tested all green for local and staging. Staging test may failed because of line break difference as mentioned in Issue 679 .
Note: Will show warning messages when run but can be ignored. The issue is addressed in this but will not patched until chromedriver2 is released. https://code.google.com/p/chromedriver/issues/detail?id=43
Status: ReadyForReview
From dam...@gmail.com on March 12, 2013 23:33:57
This issue is going to conflict with Issue 674 . We have to wait a bit until Steve completes that issue.
Blockedon: teammatespes:674
From eugenehu...@gmail.com on March 20, 2013 00:14:06
Issue to narrow down to implementing only MAC OS chrome support.
Merge with branch to resolve any possible conflicts https://code.google.com/r/eugenehuang87-teammates/source/detail?r=f07c8908c93ed956280b7d5ca66f860693eef39c&name=Issue393#
Summary: Get chrome tests running on Mac OS (was: Get chrome and safari tests running on Mac OS)
From eugenehu...@gmail.com on March 20, 2013 00:17:12
To implement MACOS Safari support, here are the issues i have encountered for future references.
LoginUIPageTest fails because assertion runs before the page is fully loaded. The page change is invoked by button clicks.
InstructorCourseDetailsPageUITest fails because modal dialog is not supported. and will not be supported due to limitation in the safari browser. https://code.google.com/p/selenium/issues/detail?id=3862 There is a workaround. But i have not tested it.
InstructorCourseAddPageUITest fails because selenium addkey for safari does not verify maxlength. I am able to insert a 30+ character into the field despite maxlength=30.
TableSortTest also fails because Safari does not allow file:// extension. https://code.google.com/p/selenium/issues/detail?id=3773 And also a number of TestCase failing from pageLoad not completed fully.
From dam...@gmail.com on March 22, 2013 18:40:31
Eugene, this one has dev green?
From dam...@gmail.com on March 23, 2013 05:33:44
Waiting for clarification.
Status: ChangesRequested
From eugenehu...@gmail.com on March 23, 2013 08:47:52
Strange, it does not have staging green right now.
There is an issue with chrome where if we start chrome and resize the window to a smaller size, most of the button clicks will be unclickable as the button will fall outside of the main view.
On InstructorEvalPageUiTest, there is a special case where the fourth row of evaluation happen to fall outside of the screen. Thus, chrome is not able to detect the location for the 'remind' button on the fourth row.
Right now, i can do a fix to maximise the chrome screen when the driver is invoked. But this will only temporarily solve the issue. In the case of future test-cases that is require clicks on elements beyond a page, the same error might appear again.
Should i proceed with the change?
From eugenehu...@gmail.com on March 24, 2013 00:56:43
Damith, did you add any comments for clarification on my clone repo?
From dam...@gmail.com on March 24, 2013 01:59:18
Yes Eugene, you can proceed with the maximizing issue. Is there a way to scroll to the bottom?
From dam...@gmail.com on May 22, 2013 08:36:55
Status: Accepted
Owner: ---