Closed Bug 586513 Opened 15 years ago Closed 15 years ago

Rename BFT test-run to General test-run

Categories

(Mozilla QA Graveyard :: Mozmill Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

Details

Attachments

(1 file)

We decided to rename the bft testrun to general, because it also contains smoketests and fft's. BFT would be too confusing. This patch renames testrun_bft.py and the BftTestRun class.
Attached patch Patch v1Splinter Review
Attachment #465015 - Flags: review?(jhammel)
Comment on attachment 465015 [details] [diff] [review] Patch v1 assuming these are all the places that need to be renamed, looks fine
Attachment #465015 - Flags: review?(jhammel) → review+
(In reply to comment #2) > assuming these are all the places that need to be renamed, looks fine Yes, I will only have to update the crowd extension to use that script from now on. Landed as: http://hg.mozilla.org/qa/mozmill-automation/rev/259e316e358e
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
This has caused a regression in the release_bft.py script: python: can't open file '..\scripts\testrun_bft.py': [Errno 2] No such file or directory
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #4) > This has caused a regression in the release_bft.py script: > > python: can't open file '..\scripts\testrun_bft.py': [Errno 2] No such file or > directory FYI, I've had to update the script manually for 4.0b4 testing. I'll revert it once complete.
(In reply to comment #5) > FYI, I've had to update the script manually for 4.0b4 testing. I'll revert it > once complete. Additionally, it seems restart tests no longer get started since this script was renamed. I'm bumping this up to blocker since it affects our release testing.
Severity: normal → blocker
(In reply to comment #4) > This has caused a regression in the release_bft.py script: > > python: can't open file '..\scripts\testrun_bft.py': [Errno 2] No such file or > directory This has nothing to do with this bug. I even haven't updated the automation scripts on that box. If you wanna stay with the head version of the repository, please edit release_bft.py and release_update.py and simply rename the file name for the target script to testrun_general.py. This bug doesn't block the release testing work. (In reply to comment #6) > Additionally, it seems restart tests no longer get started since this script > was renamed. This is another issue and should be filed as a separate bug. I wasn't able to see this last week.
Severity: blocker → normal
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
(In reply to comment #7) > This bug doesn't block the release testing work. > Thanks, I did that already as a work around. I'll leave it for now. > > Additionally, it seems restart tests no longer get started since this script > > was renamed. > > This is another issue and should be filed as a separate bug. I wasn't able to > see this last week. I'm getting no results on brasstacks for restart tests from release_bft.py on any platform. I'll file a separate bug for this. Thanks.
Move of Mozmill related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Component: Mozmill Tests → Mozmill Automation
Product: Testing → Mozilla QA
QA Contact: mozmill-tests → mozmill-automation
Whiteboard: [mozmill-automation]
Version: Trunk → unspecified
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: