[Koha-bugs] [Bug 7677] New area in subscriptions and new function when receiving

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7677

Paola Rossi <paola.rossi at cineca.it> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA

--- Comment #46 from Paola Rossi <paola.rossi at cineca.it> ---
I've applied the patches against master 3.19.00.003
[it needed a trivial rebase]

I set "makePreviousSerialAvailable" syspref to "Make" as required.
I kept the "item-level_itypes" syspref to "specific item".

I created a subscription, which didn't create an item record when it received
the serial. When I received ("Arrived") issues, no item was created: so this
bug is not about this case.

So I created another subscription, which created an item record when receiving
the serial, and I set its 2 new fields ["Item type" and "Previous item type"]
to "Continuing Resources".

Then I "Edited" the subscription:
the "Item type" and "Previous item type" fields were not set to "Continuing
Resources" anymore! (ERROR)

Anyway I went on:
Was the previously received serial's itemtype set as defined in the
subscription?

When I received ("Arrived") an issue [in DB: table serial] of the subscription
(the first issue), I saw that the default value of the:
"y - Koha item type" field
of the new item was set to nothing (why?).

I didn't change it to "Continuing Resources" [because koha should
do it for me, shouldn't it?]; then I filled the other fields (barcode, aso),
and I saved the new item.

Then I looked at the biblio:
In the biblio's Holdings tag, the item was "Available" and its item type is CR
as required (RIGHT).

I received another issue [the 2-nd] for the same subscription.
Now, in the biblio's Holdings, the new (2-nd) item was "Available" and CR, as
required.
But the previous (1-st) item [still "Available"] lost its type: it had no type
anymore! (ERROR)

But I could have been wrong: as Katrin wrote in comment 38:
>It would be good to add a test plan and description. I think
>the feature evolved a bit over time, as this is one of the older bug reports.

Anyway:
prove t/db_dependent/Serials_2.t
t/db_dependent/Serials_2.t .. 3/40
#   Failed test 'With IndependentBranches, superserials can edit a subscription
from his branch'
#   at t/db_dependent/Serials_2.t line 106.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, superserials can edit a subscription
from another branch'
#   at t/db_dependent/Serials_2.t line 109.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, superserials can show a subscription
from his branch'
#   at t/db_dependent/Serials_2.t line 112.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, superserials can show a subscription
from another branch'
#   at t/db_dependent/Serials_2.t line 115.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, edit_subscription can edit a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 121.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, show_subscription can show a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 127.
#          got: '0'
#     expected: '1'

#   Failed test 'With IndependentBranches, renew_subscription can show a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 141.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, superserials can edit a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 166.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, superserials can edit a
subscription from another branch'
#   at t/db_dependent/Serials_2.t line 169.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, superserials can show a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 172.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, superserials can show a
subscription from another branch'
#   at t/db_dependent/Serials_2.t line 175.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, edit_subscription can edit a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 180.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, edit_subscription can edit a
subscription from another branch'
#   at t/db_dependent/Serials_2.t line 183.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, show_subscription can show a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 186.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, show_subscription can show a
subscription from another branch'
#   at t/db_dependent/Serials_2.t line 189.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, renew_subscription cannot show a
subscription from his branch'
#   at t/db_dependent/Serials_2.t line 200.
#          got: '0'
#     expected: '1'

#   Failed test 'Without IndependentBranches, renew_subscription cannot show a
subscription from another branch'
#   at t/db_dependent/Serials_2.t line 203.
#          got: '0'
#     expected: '1'
# Looks like you failed 17 tests of 40.
t/db_dependent/Serials_2.t .. Dubious, test returned 17 (wstat 4352, 0x1100)
Failed 17/40 subtests

Test Summary Report
-------------------
t/db_dependent/Serials_2.t (Wstat: 4352 Tests: 40 Failed: 17)
  Failed tests:  9-13, 15, 19, 25-32, 35-36
  Non-zero exit status: 17
Files=1, Tests=40,  8 wallclock secs ( 0.01 usr  0.04 sys +  0.29 cusr  2.21
csys =  2.55 CPU)
Result: FAIL
------------------------------------------------------------------------------
So I pass the patch to "Failed QA" status.

-- 
You are receiving this mail because:
You are watching all bug changes.