Open
Bug 482779
Opened 16 years ago
Updated 2 years ago
Add litmus tests for -file command-line argument handling
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
People
(Reporter: humph, Unassigned)
Details
From bug 290057 comment 184, we need tests for the new -file command line argument, and it can't be tested in an automated way.
There are two cases that need to be tested. NOTE: these tests depend on attachment 358454 [details] [diff] [review] from bug 290057 being landed on 1.9.1.
Test 1: Passing -file when browser not running
----------------------------------------------
Assuming a browser at ~/Firefox.app
Steps:
------
1. Create a simple text file:
$ echo "Hello world" > ~/test.txt
2. Run your browser, passing the file name as a -file argument:
$ ~/Firefox.app/Contents/MacOS/firefox -file ~/test.txt
Result:
-------
New browser should open with the contents of ~/test.txt displayed in a tab.
Test 2: Passing -file when browser running
------------------------------------------
Assuming a browser at ~/Firefox.app
Steps:
------
1. Run your browser:
$ ~/Firefox.app/Contents/MacOS/firefox
2. Create a simple text file:
$ echo "Hello world" > ~/test.txt
3. Attempt to open the file:
$ open -a ~/Firefox.app/Contents/MacOS/firefox-bin -file ~/test.txt
Result:
-------
The running browser should have a new tab created with the contents of ~/test.txt displayed in the tab.
Not sure if this needs wanted1.9.1?, but setting to reflect the fact that this needs to go with that branch.
Flags: wanted1.9.1?
Flags: in-litmus?
Updated•16 years ago
|
Component: Cmd-line Features → General
Flags: wanted1.9.1?
Product: Core → Firefox
QA Contact: cmd-line → general
Version: 1.9.1 Branch → unspecified
Reporter | ||
Updated•12 years ago
|
Flags: in-litmus?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•