Bug 18697: Adjusting unit tests for weekly serial frequencies
commit2851d186f6c3376c0ae2b55b1e8c63bda87fded8
authorMarcel de Rooy <m.de.rooy@rijksmuseum.nl>
Tue, 30 May 2017 13:56:22 +0000 (30 15:56 +0200)
committerFridolin Somers <fridolin.somers@biblibre.com>
Thu, 29 Jun 2017 07:14:04 +0000 (29 09:14 +0200)
treef4eab8583cc2af5c9ee70678b9225b1f3b446c1c
parentdae1a7ccdf49b8d99748a659c6fff80185980e7f
Bug 18697: Adjusting unit tests for weekly serial frequencies

Corrections and added unit tests following the changes of the first patch.

GetFictiveIssueNumber.t: New subtest for weekly frequencies.

GetNextDate.t: Correcting a few dates one day. If we use 2/week, we will
calculate an interval of 3 days and correct with 4 days at the end of
the cycle. The connection with firstacqui is not relevant anymore.

Test plan:
[1] Run t/db_dependent/Serials/GetFictiveIssueNumber.t
[2] Run t/db_dependent/Serials/GetNextDate.t

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Signed-off-by: Josef Moravec <josef.moravec@gmail.com>
Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
(cherry picked from commit e25f4670f36e53db44931cbbcfb3c5df2125c71a)
Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
t/db_dependent/Serials/GetFictiveIssueNumber.t
t/db_dependent/Serials/GetNextDate.t