https://wiki.evergreen-ils.org/ 2026-04-29T04:22:56+00:00 https://wiki.evergreen-ils.org/ https://wiki.evergreen-ils.org/lib/exe/fetch.php?media=wiki:logo.svg text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:buildbot&rev=1644518097&do=diff Buildbot master and slave buildbot is a continuous integration server that checks the quality of the OpenSRF and Evergreen build trees after every commit. The build results are visible at <http://testing.evergreen-ils.org/buildbot/> Setting up the buildbot master * Install buildbot prereqs: <http://buildbot.net/buildbot/docs/current/manual/installation.html> * text/html 2024-12-01T16:20:33+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:debugging_perl_unit_tests&rev=1733070033&do=diff Using a debugger in Perl unit tests It can be difficult to use the Perl debugger to debug Evergreen's Perl code while the system is running.  One workaround is to run a unit test that calls the Perl code you'd like to debug.  This approach allows you to provide specific known values to the subroutines in question. text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:performance_draft_rfp&rev=1644518097&do=diff DRAFT RFP for Software Performance Evaluation Note: This document is a draft posted here to get feedback from the larger Evergreen community. The final document may differ significantly from what has been posted here. Introduction The Massachusetts Library Network Cooperative (MassLNC) is seeking proposals for consulting services to conduct a software performance evaluation of the Evergreen Integrated Library System (ILS). text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:performance_issues&rev=1644518097&do=diff Evergreen Performance Analysis Use the space below to identify areas in Evergreen that would benefit from a performance analysis along with any questions that you would like a performance analysis to answer. Staff Client * Acquisitions - There are a lot of slow areas in the acquisitions. The following are some specifics I can identify at the moment text/html 2022-02-10T18:34:57+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:performance_report&rev=1644518097&do=diff Summary Report for Evergreen Performance Evaluation OmniTI performed an Evergreen software evaluation on Evergreen this past fall on behalf of the Massachusetts Library Network Cooperative. The performance evaluation evaluated the Evergreen database, staff client and messaging framework. The study was mostly funded with a Library Services and Technology Act grant authorized through the Massachusetts Board of Library Commissioners along with some funds from MassLNC. text/html 2024-08-21T14:32:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.evergreen-ils.org/doku.php?id=dev:testing:plan&rev=1724250727&do=diff Testing Plans Started these plans regarding testing during the Evergreen Hack-A-Way 2012. Easy wins * Source code analysis (could all be tied to git hooks) [Dan Scott] * POD * template compilation * perlcritic * pgtap [Galen Charlton]