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

23 lines
489 B
PHP

<?php
use PhpOffice\PhpSpreadsheet\Calculation\Information\ExcelError;
return [
[1900, 0],
[1900, 1],
[1991, 33333.33],
[1960, '22269.0'],
[1983, 30348.0],
[1984, 30843.0],
[2525, '01 Jan 2525'],
[1918, '11-Nov-1918'],
[1904, '28-Feb-1904'],
[ExcelError::NAN(), -10],
[ExcelError::VALUE(), '31-Dec-1899'],
[ExcelError::VALUE(), 'ABCD'],
[1900, false],
[1900, true],
[1900, 366], // because of fake leap day
[1901, 367],
];