6 More Discussions You Might Find Interesting
1. SCO
hi
Howto install iperf on SCO OpenServer 5.0.7? (0 Replies)
Discussion started by: ccc
0 Replies
2. SCO
Hi,
Im installing sco openserver 5 (OpenServer-5.0.7Hw-10Jun05_1800.iso) on a vmware server 1.0.4.
Installation is ok but on when x server is loading i just can login, mouse does not move and most of keyboard cases do not respond.
I choose usb mouse + french keyboard while installating, should i... (1 Reply)
Discussion started by: sup69
1 Replies
3. SCO
Hi
I am trying to install NIC FastNic 10/100 PCI Ethernet driver into PCI# 3 of the GA-SIML Rev 1.0 Motherboard on 1GB Hard-disk driveI have following the instruction on the CD-Disk and when I added NIC by netconfig and I do not know what is the following question:
PCI BUS#
DEVICE#... (3 Replies)
Discussion started by: TinhNhi
3 Replies
4. SCO
Even though IBM states that the x3500 server is Openserver 6.x compatible, it is still a bit of a trick to install SCO Openserver 6 to the machine because the standard method of installing the BTLD required to install the OS requires that the driver be written to a floppy which doesn't exist on... (3 Replies)
Discussion started by: qkrenge
3 Replies
5. UNIX for Dummies Questions & Answers
I have just been made responsible for setting up Apache on our office SCO
box. I have searched the internet, but
haven't found any details that I can make
sense of. I'm unfamiliar with Unix and would appreciate any help members of
the forum have to offer. (1 Reply)
Discussion started by: cstovall
1 Replies
6. Filesystems, Disks and Memory
Hello all,
I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
TRIAL(1) TRIAL(1)
NAME
trial - run unit tests
SYNOPSIS
trial [ options ] [ file | package | module | TestCase | testmethod ] ...
trial --help | -h
DESCRIPTION
trial loads and executes a suite of unit tests, obtained from modules, packages and files listed on the command line.
trial will take either filenames or fully qualified Python names as arguments. Thus `trial myproject/foo.py', `trial myproject.foo' and
`trial myproject.foo.SomeTestCase.test_method' are all valid ways to invoke trial.
After running the given test suite, the default test reporter prints a summary of the test run. This consists of the word "PASSED" (if all
tests ran as expected) or "FAILED" (if any test behaved unexpectedly) followed by a count of the different kinds of test results encoun-
tered. The possible kinds of test results includes:
successes
Tests that passed all their assertions and completed without error. These are marked "PASSED" in the normal test output.
failures
Tests that failed an assertion, called self.fail() or explicitly raised self.failureException for some reason. These are marked
"FAILED" in the normal test output.
errors Tests that raised an unexpected exception (including AssertionError), tests that caused the tearDown() method to raise an exception,
tests that run for longer than the timeout interval, tests that caused something to call twisted.python.log.err() without subse-
quently calling self.flushLoggedErrors(), tests that leave the reactor in an unclean state, etc. These are marked "ERROR" in the
normal test output.
Note that because errors can be caused after the actual test method returns, it is possible for a single test to be reported as both
an error and a failure, and hence the total number of test results can be greater than the total number of tests executed.
skips Tests that were skipped, usually because of missing dependencies. These are marked "SKIPPED" in the normal test output.
expectedFailures
Tests that failed, but were expected to fail, usually because the test is for a feature that hasn't been implemented yet. These are
marked "TODO" in the normal test output.
unexpectedSuccesses
Tests that should have been listed under expectedFailures, except that for some reason the test succeeded. These are marked "SUC-
CESS!?!" in the normal test output.
OPTIONS
-b, --debug
Run the tests in the Python debugger. Also does post-mortem debugging on exceptions. Will load `.pdbrc' from current directory if it
exists.
-B, --debug-stacktraces
Report Deferred creation and callback stack traces
--coverage
Generate coverage information in the `coverage' subdirectory of the trial temp directory (`_trial_temp' by default). For each Python
module touched by the execution of the given tests, a file will be created in the coverage directory named for the module's fully-
qualified name with the suffix `.cover'. For example, because the trial test runner is written in Python, the coverage directory
will almost always contain a file named `twisted.trial.runner.cover'.
Each `.cover' file contains a copy of the Python source of the module in question, with a prefix at the beginning of each line con-
taining coverage information. For lines that are not executable (blank lines, comments, etc.) the prefix is blank. For executable
lines that were run in the course of the test suite, the prefix is a number indicating the number of times that line was executed.
The string `>>>>>>' prefixes executable lines that were not executed in the course of the test suite.
Note that this functionality uses Python's sys.settrace() function, so tests that call sys.settrace() themselves are likely to break
trial's coverage functionality.
--disablegc
Disable the garbage collector for the duration of the test run. As each test is run, trial saves the TestResult objects, which means
that Python's garbage collector has more non-garbage objects to wade through, making each garbage-collection run slightly slower.
Disabling garbage collection entirely will make some test suites complete faster (contrast --force-gc, below), at the cost of
increasing (possibly greatly) memory consumption. This option also makes tests slightly more deterministic, which might help debug-
ging in extreme circumstances.
-e, --rterrors
Print tracebacks to standard output as soon as they occur
--force-gc
Run gc.collect() before and after each test case. This can be used to isolate errors that occur when objects get collected. This
option would be the default, except it makes tests run about ten times slower.
-h, --help
Print a usage message to standard output, then exit.
--help-reporters
Print a list of valid reporters to standard output, then exit. Reporters can be selected with the --reporter option described below.
--help-reactors
Print a list of possible reactors to standard output, then exit. Not all listed reactors are available on every platform. Reactors
can be selected with the --reactor option described below.
-l, --logfile logfile
Direct the log to a different file. The default file is `test.log'. logfile is relative to _trial_temp.
-n, --dry-run
Go through all the tests and make them pass without running.
-N, --no-recurse
By default, trial recurses through packages to find every module inside every subpackage. Unless, that is, you specify this option.
--nopm Don't automatically jump into debugger for post-mortem analysis of exceptions. Only usable in conjunction with --debug.
--profile
Run tests under the Python profiler.
-r, --reactor reactor
Choose which reactor to use. See --help-reactors for a list.
--recursionlimit
Set Python's recursion limit. See sys.setrecursionlimit()
--reporter
Select the reporter to use for trial's output. Use the --help-reporters option to see a list of valid reporters.
--spew Print an insanely verbose log of everything that happens. Useful when debugging freezes or locks in complex code.
--tbformat format
Format to display tracebacks with. Acceptable values are `default', `brief' and `verbose'. `brief' produces tracebacks that play
nicely with Emacs' GUD.
--temp-directory directory
WARNING: Do not use this options unless you know what you are doing. By default, trial creates a directory called _trial_temp under
the current working directory. When trial runs, it first deletes this directory, then creates it, then changes into the directory
to run the tests. The log file and any coverage files are stored here. Use this option if you wish to have trial run in a directory
other than _trial_temp. Be warned, trial will delete the directory before re-creating it.
--testmodule filename
Ask trial to look into filename and run any tests specified using the Emacs-style buffer variable `test-case-name'.
--unclean-warnings
As of Twisted 8.0, trial will report an error if the reactor is left unclean at the end of the test. This option is provided to
assist in migrating from Twisted 2.5 to Twisted 8.0 and later. Enabling this option will turn the errors into warnings.
-u, --until-failure
Keep looping the tests until one of them raises an error or a failure. This is particularly useful for reproducing intermittent
failures.
--version
Prints the Twisted version number and exit.
--without-module modulenames
Simulate the lack of the specified comma-separated list of modules. This makes it look like the modules are not present in the sys-
tem, causing tests to check the behavior for that configuration.
-z, --random [seed]
Run the tests in random order using the specified seed.
SEE ALSO
The latest version of the trial documentation can be found at http://twistedmatrix.com/documents/current/core/howto/testing.html
AUTHOR
Written by Jonathan M. Lange
REPORTING BUGS
To report a bug, visit http://twistedmatrix.com/trac/newticket
COPYRIGHT
Copyright (C) 2003-2011 Twisted Matrix Laboratories
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Oct 2007 TRIAL(1)