Tag object that indicates a test is CPU-intensive (i.e., consumes a lot of CPU time when it runs).
Tag object that indicates a Selenium test uses the Chrome browser.
Tag object that indicates a test is disk-intensive (i.e., consumes a lot of disk-IO bandwidth when it runs).
Tag object that indicates a test is disk-intensive (i.e., consumes a lot of disk-IO bandwidth when it runs).
The corresponding tag annotation for this tag object is org.scalatest.tags.Disk
.
This tag object can be used to tag test functions (in style traits other than Spec
, in which tests are methods not functions) as being disk-intensive.
See the "tagging tests" section in the documentation for your chosen styles to see the syntax. Here's an example for FlatSpec
:
package org.scalatest.examples.tagobjects.disk
import org.scalatest._ import tagobjects.Disk
class SetSpec extends FlatSpec {
"An empty Set" should "have size 0" taggedAs(Disk) in { assert(Set.empty.size === 0) } }
Tag object that indicates a Selenium test uses the Firefox browser.
Tag object that indicates a Selenium test uses the HtmlUnit browser.
Tag that indicates a Selenium test uses the Internet Explorer browser.
Tag object that indicates a test is network-intensive (i.e., consumes a lot of network bandwidth when it runs).
Tag object that indicates a test is network-intensive (i.e., consumes a lot of network bandwidth when it runs).
The corresponding tag annotation for this tag object is org.scalatest.tags.Network
.
This tag object can be used to tag test functions (in style traits other than Spec
, in which tests are methods not functions) as being network-intensive.
See the "tagging tests" section in the documentation for your chosen styles to see the syntax. Here's an example for FlatSpec
:
package org.scalatest.examples.tagobjects.network
import org.scalatest._ import tagobjects.Network
class SetSpec extends FlatSpec {
"An empty Set" should "have size 0" taggedAs(Network) in { assert(Set.empty.size === 0) } }
Tag object that indicates a test is a candidate for retrying on either failure, cancellation, or both.
Tag object that indicates a test is a candidate for retrying on either failure, cancellation, or both.
This tag object is intended to be used in conjunction with trait Retries
, to
identify tests that are candidates for retrying.
The corresponding tag annotation for this tag object is org.scalatest.tags.Retryable
.
This tag object can be used to tag test functions (in style traits other than Spec
, in which tests are methods
not functions) as being a candidate for retries. See the "tagging tests" section in the documentation for your chosen styles to
see the syntax. Here's an example for FlatSpec
:
package org.scalatest.examples.tagobjects.retryable
import org.scalatest._ import tagobjects.Retryable
class SetSpec extends FlatSpec with Retries {
override def withFixture(test: NoArgTest) = { if (isRetryable(test)) withRetry { super.withFixture(test) } else super.withFixture(test) }
"An empty Set" should "have size 0" taggedAs(Retryable) in { assert(Set.empty.size === 0) } }
Tag object that indicates a Selenium test uses the Safari browser.
Tag object that indicates a test is slow (i.e., takes a long time to run).
Tag object that indicates a test is slow (i.e., takes a long time to run).
The corresponding tag annotation for this tag object is org.scalatest.tags.Slow
.
This tag object can be used to tag test functions (in style traits other than Spec
, in which tests are methods not functions) as being slow.
See the "tagging tests" section in the documentation for your chosen styles to see the syntax. Here's an example for FlatSpec
:
package org.scalatest.examples.tagobjects.slow
import org.scalatest._ import tagobjects.Slow
class SetSpec extends FlatSpec {
"An empty Set" should "have size 0" taggedAs(Slow) in { assert(Set.empty.size === 0) } }
Tag object that indicates a test is CPU-intensive (i.e., consumes a lot of CPU time when it runs).
The corresponding tag annotation for this tag object is
org.scalatest.tags.CPU
. This tag object can be used to tag test functions (in style traits other thanSpec
, in which tests are methods not functions) as being CPU-intensive. See the "tagging tests" section in the documentation for your chosen styles to see the syntax. Here's an example forFlatSpec
: