Closed scabug closed 13 years ago
Imported From: https://issues.scala-lang.org/browse/SI-4186?orig=1 Reporter: @wallachd Attachments:
@wallachd said: I just saw a previous Ticket on this same problem: Ticket #3735 Scaladoc should add spaces between lines.
@harrah said: as indicated, duplicate of #3735
@lindydonna said: (In r24406) Modify BufferedSource to use a BufferedLineIterator to speed up line-by-line reads on large files. Updated testfile which used this class. Closes #4186. Review (of fft.check) by prokopec.
@lindydonna said: Oops, r24406 fixes #4168 not this bug.
=== What steps will reproduce the problem (please be specific and use wikiformatting)? ===
=== What is the expected behavior? ===
Application that runs a suite of tests. The application accepts command line arguments that specify optional config map (key-value pairs), an optional runpath, zero to many Reporters, optional lists of tags to include and/or exclude, zero to many
Suite
class names, zero to many "members-only"Suite
paths, zero to many "wildcard"Suite
paths, and zero to many TestNG XML config file paths. All of these arguments are described in more detail below.A runpath is the list of filenames, directory paths, and/or URLs that Runner uses to load classes for the running test. If runpath is specified,
Runner
creates a custom class loader to load classes available on the runpath. The graphical user interface reloads the test classes anew for each run by creating and using a new instance of the custom class loader for each run. The classes that comprise the test may also be made available on the classpath, in which case no runpath need be specified.
=== What do you see instead? ===
Application that runs a suite of tests. The application accepts command line arguments that specify optional config map (key-value pairs), an optionalrunpath, zero to many Reporters, optional lists of tags to include and/or exclude, zero to manySuite class names, zero to many "members-only" Suite paths, zero to many "wildcard" Suite paths, and zero to many TestNG XML config file paths. All of these arguments are described in more detail below.
A runpath is the list of filenames, directory paths, and/or URLs that Runneruses to load classes for the running test. If runpath is specified, Runner creates a custom class loader to load classes available on the runpath. The graphical user interface reloads the test classes anew for each run by creating and using a new instance of the custom class loader for each run. The classes that comprise the test may also be made available on the classpath, in which case no runpath need be specified.
=== Additional information === (for instance, a link to a relevant mailing list discussion)
=== What versions of the following are you using? ===