Closed Bug 866011 Opened 13 years ago Closed 13 years ago

Create unit tests for FMRadio

Categories

(Firefox OS Graveyard :: Gaia::FMRadio, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mshiao, Assigned: mshiao)

Details

(Whiteboard: [TAIPEI_FND_TRACKING])

Attachments

(1 file, 1 obsolete file)

No description provided.
Summary: Create UI unit test for FMRadio → Create unit test for FMRadio
Summary: Create unit test for FMRadio → Create unit tests for FMRadio
Any update on this bug?
Flags: needinfo?(mshiao)
Whiteboard: [TAIPEI_FND_TRACKING]
(In reply to Tim Guan-tin Chien [:timdream] (MoCo-TPE) from comment #1) > Any update on this bug? Yes, I'm working on it and have the test for the frequency dialer in place. Going to continue with adding test for other portions of the app.
Flags: needinfo?(mshiao)
Attached file Link to pull request (obsolete) —
Hi Pin, I've written some unit tests for FM at the request of Tim. Can you please review and let me know your thoughts? Thanks, Mark
Attachment #747811 - Flags: review?(pzhang)
(In reply to Mark Shiao from comment #3) > Created attachment 747811 [details] > Link to pull request > > Hi Pin, > > I've written some unit tests for FM at the request of Tim. Can you please > review and let me know your thoughts? > > Thanks, > Mark Cool~ I will dive into the details, and feedback you later.
(In reply to Pin Zhang [:pzhang] from comment #4) > (In reply to Mark Shiao from comment #3) > > Created attachment 747811 [details] > > Link to pull request > > > > Hi Pin, > > > > I've written some unit tests for FM at the request of Tim. Can you please > > review and let me know your thoughts? > > > > Thanks, > > Mark > > Cool~ > I will dive into the details, and feedback you later. Havn't go through the whole patch, sorry for one quick question about this: mozFMRadio = { frequencyLowerBound: 87.5, frequencyUpperBound: 108 }; I faked a mozFMRadio object in fm/js/fm.js, so I can write the UI on desktop, does the above codes override the faked object? If yes, how about the other interfaces of mozFMRadio? and why don't we just use the mozFMRadio object defined in fm/js/fm.js?
(In reply to Pin Zhang [:pzhang] from comment #4) > (In reply to Mark Shiao from comment #3) > > Created attachment 747811 [details] > > Link to pull request > > > > Hi Pin, > > > > I've written some unit tests for FM at the request of Tim. Can you please > > review and let me know your thoughts? > > > > Thanks, > > Mark > > Cool~ > I will dive into the details, and feedback you later. @Mark, I have commented your pr, please check it. I have one question about test-suite naming, do we have any convention? Like this: suite('#favorite list', function() { Intuitively, #favorite should be a CSS-selector, i.e. a node which is named `favorite`, but we only defined `fav-list` in the index.html.
(In reply to Pin Zhang [:pzhang] from comment #6) > (In reply to Pin Zhang [:pzhang] from comment #4) > > (In reply to Mark Shiao from comment #3) > > > Created attachment 747811 [details] > > > Link to pull request > > > > > > Hi Pin, > > > > > > I've written some unit tests for FM at the request of Tim. Can you please > > > review and let me know your thoughts? > > > > > > Thanks, > > > Mark > > > > Cool~ > > I will dive into the details, and feedback you later. > > @Mark, I have commented your pr, please check it. > > I have one question about test-suite naming, do we have any convention? Like > this: > suite('#favorite list', function() { > > Intuitively, #favorite should be a CSS-selector, i.e. a node which is named > `favorite`, but we only defined `fav-list` in the index.html. Hi Pin, I've updated with your changes. Please have a look and let me know what you think. Thanks, Mark
Comment on attachment 747811 [details] Link to pull request > > Hi Pin, > > I've updated with your changes. Please have a look and let me know what you > think. > > Thanks, > Mark Hi, @Mark, it looks good to me, I have commented about the nits, please fix them, and then r=me. BTW, I think you can squash all the commits to keep the history more cleaner, :)
Attachment #747811 - Flags: review?(pzhang) → review+
Attached file Link to pull request
Hi Pin, Updated and ready for final review Thanks, Mark
Attachment #747811 - Attachment is obsolete: true
Attachment #749672 - Flags: review?(pzhang)
Comment on attachment 749672 [details] Link to pull request (In reply to Mark Shiao from comment #9) > Created attachment 749672 [details] > Link to pull request > > Hi Pin, > > Updated and ready for final review > > Thanks, > Mark Hi Mark, there is still one formatting nit you missed I think, the other parts look good enough to me, r=me It would be just a nit fixing, and I think you don't have to ask for another review, :), and thanks for your nice work.
Attachment #749672 - Flags: review?(pzhang) → review+
landed on master
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Hey, I _think_ these tests are not working, see https://travis-ci.org/mozilla-b2g/gaia/builds/7221960
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: