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

22 lines
451 B
PHP

<?php
use PhpOffice\PhpSpreadsheet\Calculation\Information\ExcelError;
// OpenOffice Result, Argument
return [
[19, 22269],
[1, 30348],
[10, 30843],
[11, '11-Nov-1918'],
[28, '28-Feb-1904'],
[ExcelError::VALUE(), '30-Feb-1904'],
[ExcelError::VALUE(), 'Invalid'],
// The following will all differ between Excel and OpenOffice
[29, -1],
[31, 1],
[30, 0.5],
[30, 0],
[31, true],
[30, false],
];