Confirmed users
425
edits
TestEngineering/Web/Automation/Gaia UI Testing: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Web/Automation/Gaia UI Testing (view source)
Revision as of 02:15, 18 November 2013
, 18 November 2013no edit summary
No edit summary |
|||
| Line 69: | Line 69: | ||
## This can also be done by pasting the url to the Github pull request into an attachment to the bug using 'paste text as attachment'. | ## This can also be done by pasting the url to the Github pull request into an attachment to the bug using 'paste text as attachment'. | ||
## Flag the attachment for review and add a comment that this patch is to uplift to the branch of interest. | ## Flag the attachment for review and add a comment that this patch is to uplift to the branch of interest. | ||
== Keeping On Top of Changes == | |||
There are some steps that can be taken to try to keep the branches in sync. These include: | |||
# As mentioned above, if you can complete an uplift yourself, by creating a pull request, rather than simply flagging a bug as affected, that is preferable. | |||
# Monitor bugs that are flagged as ''status-b2g-v1.2: affected'', and complete the uplifts for those. You can use a [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=gaia-ui-test-open-v1.2-affected&sharer_id=440009&list_id=8605601 shared Bugzilla query] that was created for this purpose to view such bugs. | |||
# Complete an audit of commits that have landed in master but not v1.2. | |||
## You can use the command <code>git show master ^v1.2 --no-merges -- tests/python/gaia-ui-tests</code> to show all such commits. | |||