Closed
Bug 358985
Opened 19 years ago
Closed 16 years ago
Calendar automated testing/QA extension
Categories
(Calendar :: Internal Components, enhancement)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jminta, Unassigned)
Details
Attachments
(1 file)
|
61.17 KB,
patch
|
Details | Diff | Splinter Review |
This is a bug for the development and initial landing of an extension for QA and automated testing of Sunbird and Lightning.
After talking things over with Clint, the current available automated testing tools for Mozilla would take an inordinate amount of effort to port to our needs. Instead, a homegrown solution will likely be a more effective use of resources.
| Reporter | ||
Comment 1•19 years ago
|
||
This is a current snapshot of the extension. The current TODO list looks something like:
-localize strings
-create makefile magic to build the extension when --enable-tests is used
-fix bug in update system (always pings the server, rather than only when the file is expired, based on pref)
-decide on/tweak location for remote tests (the extension currently points to my own private webspace.)
The files in remote/ correspond to the files that would be hosted in the remote tests location.
I'm unsure which of these TODO items should be accomplished prior to initial landing, but Clint suggested that getting this in the tree sooner rather than later would be a good thing.
Assignee: nobody → jminta
Status: NEW → ASSIGNED
| Reporter | ||
Comment 2•18 years ago
|
||
Re-assigning my bugs to nobody@mozilla.org due to recent developments.
Assignee: jminta → nobody
Status: ASSIGNED → NEW
Seeing the patch, were any of these supposed to be included in it?
? calendar/test/qa-extension/calQA.xpi
? calendar/test/qa-extension/chrome
? calendar/test/qa-extension/chrome.manifest.txt
? calendar/test/qa-extension/content
? calendar/test/qa-extension/tests-stage.js
? calendar/test/qa-extension/tests-stage2.js
? calendar/test/qa-extension/tests-stage4.js
| Reporter | ||
Comment 4•18 years ago
|
||
(In reply to comment #3)
> Seeing the patch, were any of these supposed to be included in it?
>
> ? calendar/test/qa-extension/calQA.xpi
> ? calendar/test/qa-extension/chrome
> ? calendar/test/qa-extension/chrome.manifest.txt
> ? calendar/test/qa-extension/content
No, these are intermediate files created during extension packaging. The build system would take care of these.
> ? calendar/test/qa-extension/tests-stage.js
> ? calendar/test/qa-extension/tests-stage2.js
> ? calendar/test/qa-extension/tests-stage4.js
>
These were additional copies of the test-suite, so I could test the remote-downloading of newer sets of test-suites. They are not needed, the patch should be correct as is.
Comment 5•16 years ago
|
||
Yeah to automated tests with MozMill.
Archaeopteryx: mschroeder: i shall ask you if i can mark bug
meschroeder: Archaeopteryx: better resolving as invalid
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•