Closed Bug 1810101 Opened 1 year ago Closed 1 year ago

Use "add_task()" instead of "add_test()" in Remote Protocols xpcshell tests

Categories

(Remote Protocol :: Agent, task, P3)

task

Tracking

(firefox112 fixed)

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: whimboo, Assigned: ofrazy, Mentored)

Details

(Whiteboard: [lang=js])

Attachments

(1 file, 4 obsolete files)

All of our xpcshell tests currently use the "add_test()" function which require the line run_next_test(); to be added at the end of the test:

https://searchfox.org/mozilla-central/search?q=add_test&path=remote%2F&case=false&regexp=false

We should switch to add_task() which doesn't need it and better works with async test code.

Mentor: hskupin
Priority: -- → P3
Whiteboard: [lang=js]

Hello, I am new here but I have found interest in this bug and I would love to solve it, how do I go about it? I'd love to contribute to this project.

Flags: needinfo?(hskupin)

You are welcome to get started! I would suggest that you have a look at our general documentation in how to get started:
https://firefox-source-docs.mozilla.org/remote/index.html

If something is unclear don't hesitate to ask here, or join us on Element / Matrix as described in the docs. Thanks.

Flags: needinfo?(hskupin)

(In reply to Henrik Skupin [:whimboo][⌚️UTC+1] (away 02/13 - 02/19) from comment #2)

You are welcome to get started! I would suggest that you have a look at our general documentation in how to get started:
https://firefox-source-docs.mozilla.org/remote/index.html

If something is unclear don't hesitate to ask here, or join us on Element / Matrix as described in the docs. Thanks.

Hello Henrik,
So I've just looked at the codebase on GitHub and I have managed to track the files that need the changes, should I fork the repo and then link the bug once I am done, or there is another process that I should follow to fix the issue addressed in this bug?

On Github we only have a copy of the source. Check the following pages specifically in how to get started:

https://firefox-source-docs.mozilla.org/testing/marionette/NewContributors.html
https://firefox-source-docs.mozilla.org/testing/marionette/Building.html

ofrazy, are you still interested to work on this bug? Is there anything blocking you and where I can help? Please let me know.

Flags: needinfo?(ofrazy)

(In reply to Henrik Skupin [:whimboo][⌚️UTC+1] from comment #5)

ofrazy, are you still interested to work on this bug? Is there anything blocking you and where I can help? Please let me know.

Yes, I am interested

I had lost hold of my devices, I am currently setting up my environment I will be in contact with you on element incase of any issues.

Flags: needinfo?(ofrazy)
Assignee: nobody → ofrazy
Status: NEW → ASSIGNED
Attachment #9319549 - Attachment description: WIP: Bug 1810101 used add_task() instead of add_test() → Bug 1810101 used add_task() instead of add_test()

Depends on D170809

Attachment #9319663 - Attachment description: Bug 1810101 changed all instances of add_task() → Bug 1810101 - Use async for all instances of add_task()
Attachment #9319663 - Attachment is obsolete: true

Depends on D170809

Attachment #9319899 - Attachment is obsolete: true

Depends on D170809

Depends on D171059

Attachment #9319965 - Attachment is obsolete: true
Attachment #9320018 - Attachment is obsolete: true
Attachment #9319549 - Attachment description: Bug 1810101 used add_task() instead of add_test() → Bug 1810101 - [remote] Use add_task() instead of add_test() for xpcshell tests.
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d55d82d13a8
[remote] Use add_task() instead of add_test() for xpcshell tests. r=webdriver-reviewers,whimboo
Regressions: 1819278
No longer regressions: 1819278
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: