9 calls to ViewsDataTest::setUpMockModuleHandler()
- ViewsDataTest::setUpMockModuleHandlerWithExpectation in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Reinitializes the module handler as a mock object with an expectation.
- ViewsDataTest::testCacheCallsWithSameTableMultipleTimesAndWarmCache in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache calls for a single table and warm cache.
- ViewsDataTest::testCacheCallsWithWarmCacheAndDifferentTable in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache calls for a different table than the one in cache.
- ViewsDataTest::testCacheCallsWithWarmCacheAndGetAllTables in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache calls for all views data.
- ViewsDataTest::testCacheCallsWithWarmCacheAndInvalidTable in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache calls for a non-existent table.
- ViewsDataTest::testCacheCallsWithWarmCacheForInvalidTable in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache calls for a non-existent table.
- ViewsDataTest::testConcurrentFiberAccess in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests that concurrent fibers retrieving views data cache entries correctly.
- ViewsDataTest::testFullAndTableGetCache in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests the cache of the full and single table data.
- ViewsDataTest::testFullyLoadedPropertySetAfterCacheLoad in core/
modules/ views/ tests/ src/ Unit/ ViewsDataTest.php - Tests that fullyLoaded is TRUE when data is loaded from cache.
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.