From fc01eef111c8b5a74d38b42480b82afe8d838080 Mon Sep 17 00:00:00 2001 From: Alex Pott Date: Mon, 16 Feb 2015 14:48:53 +0000 Subject: [PATCH] Issue #2424761 by rodrigoaguilera: Update automated tests documentation to reflect the removal of getInfo --- core/modules/system/core.api.php | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/core/modules/system/core.api.php b/core/modules/system/core.api.php index afd4ae26ad8..407e439ee7d 100644 --- a/core/modules/system/core.api.php +++ b/core/modules/system/core.api.php @@ -895,8 +895,8 @@ * where yourmodule is your module's machine name. * - The test class file must be named and placed under the yourmodule/tests/src * directory, according to the PSR-4 standard. - * - Your test class needs a getInfo() method, which gives information about - * the test. + * - Your test class needs a phpDoc comment block with a description and + * a @group annotation, which gives information about the test. * - Methods in your test class whose names start with 'test' are the actual * test cases. Each one should test a logical subset of the functionality. * For more details, see: @@ -928,8 +928,8 @@ * where yourmodule is your module's machine name. * - The test class file must be named and placed under the yourmodule/src/Tests * directory, according to the PSR-4 standard. - * - Your test class needs a getInfo() method, which gives information about - * the test. + * - Your test class needs a phpDoc comment block with a description and + * a @group annotation, which gives information about the test. * - You may also override the default setUp() method, which can set be used to * set up content types and similar procedures. * - In some cases, you may need to write a test module to support your test;