Closed Bug 595900 Opened 14 years ago Closed 10 years ago

TBPL needs unit tests

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Swatinem, Unassigned)

References

Details

TBPL needs unit tests desperately, so things don’t break on every other checkin.
I must say I have zero experience testing interactive websites that depend on foreign apis, for posting comments on bugzilla or staring builds on tinderbox.

For frontend testing I guess selenium should be good, but how can we test bugzilla/tinderbox pushing reliably?
First two thoughts off the top of my head for Tinderbox: use http://tinderbox-stage.mozilla.org/ (and somehow deal with the way that you have no idea what will be failing or how at the time you run tests), or, run a test "Tinderbox" with a faked up JSON and faked logs. Dunno if the Bugzilla API is staged on landfill.bugzilla.org or not.
(In reply to comment #1)
> Dunno if the Bugzilla API
> is staged on landfill.bugzilla.org or not.

Gerv will know that.
Most regression bugs we had to deal with recently were in UserInterface.js and close friends, so I'll focus on automating that first. All communication with external things can be emulated with mock objects for a start.
There currently isn't a test install of the BzAPI available, because the Bugzilla staging server that the test install of BzAPI was pointed at got locked down due to possible security risks. I need to re-point it at a new landfill instance, but have not yet done so. It's on my list. Keep an eye on mozilla.tools for updates.

Gerv
Bugs 599425 and 599551 are victims of not having automated tests for comment submission. (And my fault of not testing that manually)
OS: Linux → All
Hardware: x86_64 → All
Depends on: 919047
Product: Webtools → Tree Management
This is fixed in Treeherder.
Wontfix here since TBPL is nearing EOL.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.