Task #55206

UpdateExtensionListTaskTest should be a functional test

Added by Oliver Hader over 7 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Tests
Start date:
2014-01-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:
Remote Sprint

Description

The UpdateExtensionListTaskTest in the extension manager package depends on extension scheduler being installed.
To have the chance to always execute these tests, the current unit test should rather be a functional test then.


Related issues

Follows TYPO3 Core - Bug #55192: Class 'TYPO3\CMS\Scheduler\Task\AbstractTask' not foundClosedStefano Kowalke2014-01-20

Actions
#1

Updated by Mathias Schreiber over 6 years ago

still valid

#2

Updated by Anja Leichsenring over 6 years ago

  • Sprint Focus set to On Location Sprint
#3

Updated by Anja Leichsenring over 5 years ago

  • Sprint Focus changed from On Location Sprint to Remote Sprint
#4

Updated by Mathias Schreiber over 5 years ago

  • Target version deleted (6.2.0)
#5

Updated by Susanne Moog over 3 years ago

  • Status changed from New to Accepted
  • Target version set to 9 LTS
#6

Updated by Susanne Moog over 2 years ago

  • Target version changed from 9 LTS to Candidate for patchlevel
#7

Updated by Susanne Moog about 1 year ago

  • Status changed from Accepted to Needs Feedback

This is currently true for all task tests in all extensions we have (all unit tests btw.).

In earlier versions we had this https://review.typo3.org/c/Packages/TYPO3.CMS/+/26954/4/typo3/sysext/extensionmanager/Tests/Unit/Task/UpdateExtensionListTaskTest.php

However, I don't really think it's necessary as the underlying problem is nowadays slightly different: in earlier versions the class loader threw a fatal error if the extension was not loaded, in current versions, it seems to be enough that the code is there and autoloaded (independent of the state of the extension itself) - meaning the core tests run in every core development setup as the code is always available. In packaged versions it isn't - but then, the tests are not available either.

I'd propose to close this issue for that reason.

#8

Updated by Benni Mack about 1 year ago

  • Status changed from Needs Feedback to Closed

Also available in: Atom PDF