Closed
Bug 1219678
Opened 10 years ago
Closed 9 years ago
Implement *test_number_keyboard.py* as an integration test in JavaScript
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(feature-b2g:2.6+)
RESOLVED
FIXED
| feature-b2g | 2.6+ |
People
(Reporter: whsu, Assigned: ralin)
References
Details
(Whiteboard: [gip-to-gij])
Attachments
(5 files)
|
46 bytes,
text/x-github-pull-request
|
Details | Review | |
|
46 bytes,
text/x-github-pull-request
|
Details | Review | |
|
46 bytes,
text/x-github-pull-request
|
timdream
:
feedback+
|
Details | Review |
|
46 bytes,
text/x-github-pull-request
|
timdream
:
review+
|
Details | Review |
|
46 bytes,
text/x-github-pull-request
|
timdream
:
review+
|
Details | Review |
| Reporter | ||
Updated•10 years ago
|
Component: Gaia::UI Tests → Gaia::Keyboard
Updated•10 years ago
|
feature-b2g: --- → 2.6+
Comment 1•10 years ago
|
||
Ray will take a look, thanks!
Assignee: nobody → ralin
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•10 years ago
|
||
since number input type is not covered by gij now, I'll implement this part(as link shown) to a new suite in gij.
https://github.com/mozilla-b2g/gaia/blob/e68d693cb55fb5d8946498eb2bdb63f55116d38e/tests/python/gaia-ui-tests/gaiatest/tests/functional/keyboard/test_number_keyboard.py#L20-L30
Comment 3•10 years ago
|
||
Comment 4•10 years ago
|
||
Comment 5•10 years ago
|
||
| Assignee | ||
Comment 6•10 years ago
|
||
Comment on attachment 8684798 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij > mozilla-b2g:master
1. this test is now covered by the following code segment in gij.
https://github.com/raylin/gaia/blob/66ac0dc10073bfa300f9cfb568b936bf3a86e89e/apps/keyboard/test/marionette/number_keyboard_test.js#L50-L90
2. moved input_test.js to text_keyboard_test.js
Attachment #8684798 -
Flags: review?(timdream)
Comment 7•10 years ago
|
||
Comment on attachment 8684798 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij > mozilla-b2g:master
Nice work! I've left a few comments on GitHub.
Please make sure your work is not just about translate Python code to JavaScript, but also read and evaluate the test cases to see if the assertions and operations are actually valid. We don't want to add false positive tests :).
Attachment #8684798 -
Flags: review?(timdream) → feedback+
Comment 8•10 years ago
|
||
| Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
| Assignee | ||
Comment 9•10 years ago
|
||
Comment on attachment 8685304 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij-r1 > mozilla-b2g:master
try to refine prior commit and follow the principles in comments.
Attachment #8685304 -
Flags: review?(timdream)
Updated•10 years ago
|
Keywords: checkin-needed
Comment 10•10 years ago
|
||
Comment on attachment 8685304 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij-r1 > mozilla-b2g:master
This is a very nice re-organization of the tests. Thank you for doing this.
Preferably if a set of re-arrangement of code is needed before actually implementing the test, these underlining work should be split into another "Part I" commit (you can land multiple commits in a pull request as long as they all begin with a Bug #).
If the re-arrangement is larger than desired, you could also file a dependent bug and work/review/land that patch in that bug too.
Attachment #8685304 -
Flags: review?(timdream) → review+
Comment 11•10 years ago
|
||
| Assignee | ||
Comment 12•10 years ago
|
||
Comment on attachment 8685924 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij-r2 > mozilla-b2g:master
Thanks a lot for your kind information. It does meet my questions and help me to improve my workflow. If possible, I'm willing to polish gij in Keyboard app after these five bugs.
I updated the non-descriptive comment.
Thanks.
Attachment #8685924 -
Flags: review?(timdream)
Comment 13•10 years ago
|
||
Comment on attachment 8685924 [details] [review]
[gaia] raylin:1219678-test-number-keyboard-gij-r2 > mozilla-b2g:master
No need to seek r+ once you already got one.
Also, you don't really need to file new pull requests for every review unless you explicitly want to record-keeping the changes.
Make sure you close the pull requests that shouldn't be merged.
Attachment #8685924 -
Flags: review?(timdream) → review+
| Assignee | ||
Comment 14•10 years ago
|
||
Yes, I see. I'll make it better next time.
Thanks.
| Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 15•9 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•