@runTestsInSeparateProcesses
  • References/PHP/PHPUnit/Annotations

@runTestsInSeparateProcesses Indicates that all tests in a test class should be run in a separate PHP process.

2025-01-10 15:47:30
@expectedException
  • References/PHP/PHPUnit/Annotations

@expectedException Example 2.10 shows how to use the @expectedException annotation to test whether an exception

2025-01-10 15:47:30
@testdox
  • References/PHP/PHPUnit/Annotations

@testdox

2025-01-10 15:47:30
@preserveGlobalState
  • References/PHP/PHPUnit/Annotations

@preserveGlobalState When a test is run in a separate process, PHPUnit will attempt to preserve the global state from the parent process by

2025-01-10 15:47:30
@coversNothing
  • References/PHP/PHPUnit/Annotations

@coversNothing The @coversNothing annotation can be used in the test code to specify that no code coverage information

2025-01-10 15:47:30
@codeCoverageIgnore*
  • References/PHP/PHPUnit/Annotations

@codeCoverageIgnore* The @codeCoverageIgnore, @codeCoverageIgnoreStart and

2025-01-10 15:47:30
@test
  • References/PHP/PHPUnit/Annotations

@test As an alternative to prefixing your test method names with test, you can use the @test

2025-01-10 15:47:30
@coversDefaultClass
  • References/PHP/PHPUnit/Annotations

@coversDefaultClass The @coversDefaultClass annotation can be used to specify a default namespace or class name

2025-01-10 15:47:30
@before
  • References/PHP/PHPUnit/Annotations

@before The @before annotation can be used to specify methods that should be called before each test method in

2025-01-10 15:47:30
@runInSeparateProcess
  • References/PHP/PHPUnit/Annotations

@runInSeparateProcess Indicates that a test should be run in a separate PHP process.

2025-01-10 15:47:30