Project

General

Profile

Actions

Bug #22452

closed

Test different BE setups in the page renderer unit tests

Added by Oliver Klee over 14 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-04-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.4
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

... e.g. using a data provider.

Post by Ernesto on issue #22376 in the Core NG:

This leads me to a question on the test-scenario. When certain methods
that we are testing behave differently depending on TYPO3_CONF_VARS
settings, they should test all different combinations of such, right?
And not only test the "current developers environment". What do you
think of this:

$expectedRegExp = '#<script
src="contrib/prototype/prototype\.(js|\d+\.js|js\?\d+)"
type="text/javascript"></script>#';
foreach (array(TRUE, FALSE) as
$GLOBALS['TYPO3_CONF_VARS']['BE']['versionNumberInFilename']) {
$this->fixture->loadPrototype();
$out = $this->fixture->render();
$this->assertRegExp(
$expectedRegExp,
$out
);
}

(issue imported from #M14104)

Actions #1

Updated by Alexander Opitz about 11 years ago

  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from New to Needs Feedback
Actions #3

Updated by Oliver Klee about 11 years ago

This concern probably has been solved by the functional tests for the core. So this issue now can be closed.

Actions #4

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to Closed
Actions

Also available in: Atom PDF