Closed
Bug 576289
Opened 15 years ago
Closed 14 years ago
Broken link to litmus tutorial
Categories
(quality.mozilla.org :: Content, defect, P2)
quality.mozilla.org
Content
Tracking
(Not tracked)
RESOLVED
FIXED
2.5
People
(Reporter: thetravellingbard, Assigned: coop)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier:
http://quality.mozilla.org/documents-home/test-docs/litmus-tutorial gives not found from https://litmus.mozilla.org/
Reproducible: Always
Steps to Reproduce:
1. go to https://litmus.mozilla.org/
2. click on link to the tutorial http://quality.mozilla.org/documents-home/test-docs/litmus-tutorial
Actual Results:
page not found
Expected Results:
tutorial page should be there
Many are facing this issue I too came across the same scenario and I am not able to reach the tutorial page
Please update the correct link
Jacob
Comment 2•15 years ago
|
||
Thanks for reporting this.
The tutorial seems to have been removed from QMO. There's a copy over at http://new.quality.mozilla.org/documents-home/test-docs/litmus-tutorial. Can that document get re-uploaded to QMO so that we can update the link on the litmus homepage?
Kicking this over to the QMO component until the document exists again, then it can come back to litmus.
Status: UNCONFIRMED → NEW
Component: Litmus → Content
Ever confirmed: true
Product: Webtools → quality.mozilla.org
QA Contact: litmus → content
Version: Trunk → unspecified
Assignee | ||
Comment 4•15 years ago
|
||
I've temporarily changed the tutorial link to point to the old doc, but someone should really migrate the doc over to the current QMO.
Severity: normal → major
OS: Mac OS X → All
Priority: -- → P3
Hardware: x86 → All
Updated•15 years ago
|
Target Milestone: --- → 2.5
Comment 5•15 years ago
|
||
I'm going to assign this to Tracy since he's owning the Litmus documentation. Tracy, we just need an update to the document mentioned in comment #2
Assignee: nobody → twalker
Comment 6•15 years ago
|
||
I just created http://new.quality.mozilla.org/http%3A/%252Fquality.mozilla.org/documents-home/test-docs/litmus-tutorial ???
Probably needs to be deleted. I thought I was on qmo not new.qmo. Someone that actually knows how to shuffle docs around on qmo should do this before I mess up anything else. reassigning to default owner.
Assignee: twalker → nobody
Comment 10•14 years ago
|
||
I can still see this issue - it would be nice to see it fix as people may need help in litmus.
Comment 11•14 years ago
|
||
Link is still broken.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: P3 → P2
Assignee | ||
Comment 12•14 years ago
|
||
A grievously out-of-date version is now available again in the wiki:
https://wiki.mozilla.org/Litmus:Tutorial
I've updated the links from Litmus to point to this new location.
I would encourage eager new contributors to help with updating the doc to reflect the current state of Litmus.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 13•14 years ago
|
||
Since we're hoping to have Litmus replaced in the next quarter or so, I'm not sure how much work we should put in there.
Assignee | ||
Comment 14•14 years ago
|
||
(In reply to comment #13)
> Since we're hoping to have Litmus replaced in the next quarter or so, I'm not
> sure how much work we should put in there.
I've been waiting 4 years for this replacement to materialize. I'm hopeful for the new version too, but also realistic. Better to have some docs in place in case things are delayed further.
Comment 15•14 years ago
|
||
I match your cynicism and raise you a dose of jaded.
What would you like to see done on this wiki page? Any suggestions?
Assignee | ||
Comment 16•14 years ago
|
||
Some thoughts:
* Removing the branch-specific notes under "Setup a Test," or mapping them to the new state of the world with nightly/aurora/beta.
* Adjusting the workflow to what happens on testdays these days.
* moar hyperlinks to docs, static pages within Litmus, bugzilla, etc.
You need to log in
before you can comment on or make changes to this bug.
Description
•