Evergreen DokuWiki - qa

billing_test_cases

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Below are test cases used when testing the Conditional Negative Balances branch and identify some combinations of settings that should be tested when changes are made to billing. 1. No Prohibit Negative Balance Settings Are Enabled, Payment Made Note: tested with negative balance settings unset and with

concerto_logins

Anonymous (anonymous@undisclosed.example.com) — 2024-10-09T19:42:37+00:00

Sample Data Sets (often called "Concerto" and "Enhanced Concerto") Evergreen comes with two sets of sample data called Concerto and Enhanced Concerto. These data sets can be used for writers, developers, testers and evaluators. Concerto includes 100 bibliographic records retrievable with the keyword "concerto", 100 French bibliographic records, as well as patron records with circ transactions, including some holds and some overdue items.

eg_test_cases

Anonymous (anonymous@undisclosed.example.com) — 2024-08-13T20:31:18+00:00

Test Cases for Evergreen These are test cases designed to test core functionality of Evergreen out of the box. They are based very loosely on testcases from See the GPLS/PINES Evergreen Test Cases too. Here are some more Generic Testing Guidelines from Sitka. SCL-001a: Staff Client Login * Log in as "admin" or Global Admin account, register a new workstation at BR1 called "Test"

enhanced_concerto_bib_records

Anonymous (anonymous@undisclosed.example.com) — 2024-06-29T00:40:49+00:00

Bib Record ID Deleted? Serial? Lang Author (normalized) Title Proper (normalized) 1 No Baldazzi, Gianfranco. La canzone italiana del Novecento : da Piedigrotta al Festival di Sanremo, dal caffè-concerto all'opera rock, una storia della società italiana attraverso le sue canzoni più belle e i loro grandi interpreti : da Enrico Caruso a Eros Ramazzotti

enhanced_concerto_org_unit_table

Anonymous (anonymous@undisclosed.example.com) — 2024-06-27T16:33:25+00:00

Workstations can be registered at those organizational units displayed in boldface. Depth Type Name Short Name Parent Short Name Enhanced Data 0 Consortium Example Consortium

enhanced_concerto_patron_accounts

Anonymous (anonymous@undisclosed.example.com) — 2024-07-01T13:48:14+00:00

* Patron accounts with a starting digit of 8 have a password of demo123 when logging into My Account for the Evergreen ILS OPAC. * Patron accounts with a starting digit of 9 will need to have their password reset via the Evergreen ILS client. *

enhanced_concerto_staff_accounts

Anonymous (anonymous@undisclosed.example.com) — 2024-07-01T14:02:17+00:00

* Staffs accounts with a barcode starting digit of 8 have a password of demo123 when logging into the Evergreen ILS client. * Staff accounts with a barcode starting digit of 9 will need to have their password reset via the Evergreen ILS client.

enhanced_concerto

Anonymous (anonymous@undisclosed.example.com) — 2024-09-19T17:50:02+00:00

Enhanced Concerto Data Set The Enhanced Concerto data set was developed through a collaborative effort in the Evergreen Community. The purpose of the enhanced data set is to provide a richer data environment for ease of testing and evaluation of the Evergreen open-source ILS.

generic_testing_guidelines

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Test Checklist Searching Try * Searching from Home Screen * Try different keyword/author/subject * Try different formats (video/etc) * Try different org units * Searching from Advanced Search * Try different keyword/author/subject

gpls_pines_evergreen_test_cases

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

GPLS/PINES Evergreen Test Cases Based on the work from this page, GPLS/PINES staff have been working up test cases for versions 1.4.0.7 and 1.6.1.7 of Evergreen, with plans to add and adapt. This will begin as a dumping ground for what we have so far, and we will clean up and better organize these as we go. We're also considering adapting something like

new_xul_testing

Anonymous (anonymous@undisclosed.example.com) — 2022-02-10T18:34:57+00:00

Testing New XULRunner Branch The new XULRunner Branch makes the Evergreen staff client more compatible with newer versions of XULRunner. To ensure that it is merged into Evergreen with as few bugs as possible, we need volunteers to test this branch in all areas of the staff client.

preventing_regressions

Anonymous (anonymous@undisclosed.example.com) — 2025-07-30T13:35:21+00:00

Preventing regressions You've fixed a bug in Evergreen! That's great! However, there's a dark side. Most bugs happen because they are perfectly reasonable mistakes to make. Therefore, another perfectly reasonable contributor, not knowing about the history of your bug fix, might some day re-introduce the exact same bug that you just fixed.

testing_a_tarball

Anonymous (anonymous@undisclosed.example.com) — 2024-12-19T14:48:23+00:00

Testing a tarball This page is mainly intended for members of a release team who want to verify that they have built a tarball that will work for users. It could also be used by anybody else who wants to make sure a particular Evergreen tarball will work.

tools

Anonymous (anonymous@undisclosed.example.com) — 2024-09-18T13:46:24+00:00

Quality Assurance Tools Evergreen contributors use several tools to make sure that they are not introducing new bugs and that their contributions will be readable and maintainable in the long term. This page provides an overview of the various testing tools, what they do, and at which stage you would use them, with an emphasis on which ones you run vs which ones you write.