Difference between revisions of "EPrints 3.5.0 Testing"
(Added testing 3.5.0 page) |
m (→Spell Checking) |
||
| Line 12: | Line 12: | ||
== Spell Checking == | == Spell Checking == | ||
| − | [https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [ https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator). | + | [https://github.com/codespell-project/codespell Codespell] has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary.txt standard] and [https://raw.githubusercontent.com/codespell-project/codespell/master/codespell_lib/data/dictionary_rare.txt rare] Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator). |
== Things for beta testers to test? == | == Things for beta testers to test? == | ||
Revision as of 17:10, 3 July 2026
This page discusses the various testing carried out and to be carried out as part of the EPrints 3.5.0 release
Contents
Continuous Integration Testing
A build of EPrints 3.5 GitHub head is carried out every day with the following tested: 1. Unit tests as found under https://github.com/eprints/eprints3.5/tree/master/tests 2. User acceptance tests (written using the Selenium IDE) described at https://github.com/eprints/eprints_ci/blob/main/sides/templates/eprints35_pub.side.tmpl
Also, we are currently in the process of integrating CI with pull requests to test a build of the pull request to informed reviewers of whether it is OK to merge. These tests are written in Playwright and can be found under https://github.com/eprints/eprints3.5/tree/master/ci/pytest/eprints/ but there are only a few tests at the moment and it is a work in progress to build up a suite of tests that will ultimately be more comprehensive than the current Selenium IDE acceptance tests
Accessibility Testing
A full survey of pages in a vanilla EPrints research publication repository has been carried out using the WAVE Accessibility plugin for Firefox. The current results for this survey can be found at https://raw.githubusercontent.com/eprints/eprints3.5/refs/heads/master/lib/lang/en/static/accessibility/report.xpage or if you have deployed an EPrints instance at http://YOUR.REPOSITORY.HOSTNAME/accessibility/report.html
Spell Checking
Codespell has been run across the EPrints 3.5 codebase to detect spelling errors using a combination of the standard and rare Codespell dictionaries, which list common typos->correct spellings (e.g. seperator->separator).
Things for beta testers to test?
Obviously when developing a new EPrints repository a lot of the testing falls into two categories: 1. Testing the new features being implemented. 2. Doing stock testing of generic functionality. What is often gets missed is more niche features or just using an EPrints repository in non-standard ways. Therefore testing ingredients, plugins, etc. that don't come as part of the initial install would be really useful to get feedback. As EPrints 3.5 has quite a few changes to 3.4, then trying to deploying the whole configuration, ingredients, plugins for an archive is unrealistic. However, testing individual ingredients/plugins you will want to use on 3.5 or interesting bespoke changes to your EPrints repository, are just the sort of things we are looking for as beta test feedback.
However, to start with you probably just want to follow the current EPrints 3.5.0 RC1 installation instructions and make sure you can get an EPrints repository up and running.
Suggestions for features/aspects to test
If you have an EPrints wiki account and want to suggest things that should be tested (which don't look to have been covered above) then please add these below.
