Files
MarkBaker a91dd60a98 Refactor unit tests to ensure that assertions are in the actual test, and not in an abstract class; and that setup/teardown are in the test and not an abstract. This means that assertions and setup/teardown are always in the file when reviewing PRs.
Also enforce more rigorous Excel Function implementation by testing the underlying implementation, call via the Calc Engine, and execution from in a worksheet.
Separate out unhappy path (exception) checks into a separate test, so that a single test isn't made overcomplex checking for every potentiality.

Scrutinizer may dislike variadics, for variable number of arguments of mixed type; but tough. It's 100% valid PHP, accepted by phpstan, and makes life a lot easier.

Initial work here covers all the database and datetime unit tests for Excel function implementations.
2023-03-10 04:15:12 +01:00

26 lines
732 B
PHP

<?php
use PhpOffice\PhpSpreadsheet\Calculation\Information\ExcelError;
return [
[39493.0, '15-Jan-2008', 1],
[39431.0, '15-Jan-2008', -1],
[39522.0, '15-Jan-2008', 2],
[39202.0, '31-Mar-2007', 1],
[39141.0, '31-Mar-2007', -1],
[39507.0, '31-Mar-2008', -1],
[39416.0, '31-Mar-2008', -4],
[39141.0, '29-Feb-2008', -12],
[39248.0, '15-Mar-2007', 3],
[22269.0, 22269.0, 0],
[22269.0, 22269, 0],
[22331.0, 22269.0, 2],
[22331.0, 22269.75, 2],
[25618.0, 22269.0, '110'],
[18920.0, 22269.0, -110],
[ExcelError::VALUE(), '15-Mar-2007', 'ABC'],
[ExcelError::VALUE(), 'Invalid', 12],
[ExcelError::VALUE(), true, 12],
[ExcelError::VALUE(), '2020-01-01', false],
];