Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:testing:manual_testing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
development:testing:manual_testing [2023/04/12 16:43] – ↷ Page name changed from development:testing:checklist to development:testing:manual_testing demiankatz | development:testing:manual_testing [2023/09/07 13:29] – [Merging Record Data When IDs Change] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Testing | + | ====== |
- | In any application, | + | VuFind® uses a set of [[development: |
- | Please add your own notes to this page if you add or encounter features that you think may get lost in the shuffle without occasional testing. | ||
- | |||
- | :!: This page is fairly old and hasn't been updated in a while; in most cases, the [[https:// | ||
===== General Considerations ===== | ===== General Considerations ===== | ||
- | |||
==== Browser Testing ==== | ==== Browser Testing ==== | ||
- | * Test the interface in multiple browsers to check for display inconsistencies and Javascript incompatibilities. | + | It is a good idea to test the interface in multiple browsers to check for display inconsistencies and Javascript incompatibilities. |
- | * Firefox | + | |
- | * Internet Explorer | + | |
- | * Chrome | + | * Edge |
- | * Safari | + | * Chrome |
- | * Opera | + | * Safari |
+ | * Opera | ||
+ | |||
+ | The automated test suite typically runs in Chrome, so doing manual testing in other browsers is a good way to potentially uncover browser-specific issues. | ||
==== Input Testing ==== | ==== Input Testing ==== | ||
+ | |||
+ | Some general patterns to follow when testing new features: | ||
* Test fields stored in the database for SQL injection vulnerabilities. | * Test fields stored in the database for SQL injection vulnerabilities. | ||
Line 24: | Line 25: | ||
* Test fields where input is stored and displayed back for XSS vulnerabilities and missing HTML/URL encoding. | * Test fields where input is stored and displayed back for XSS vulnerabilities and missing HTML/URL encoding. | ||
- | ===== Specific Modules | + | If you find something that breaks, please don't just fix it -- also build an automated test to prevent regressions! |
+ | |||
+ | ===== Testing Integrations | ||
+ | |||
+ | VuFind®' | ||
+ | |||
+ | Some areas of code that benefit from this type of testing: | ||
+ | |||
+ | * Export Targets (e.g. EndNote, RefWorks, etc.) | ||
+ | * ILS Drivers (e.g. Alma, Aleph, etc.) | ||
+ | * Search Backends (e.g. EDS, Summon, WorldCat, etc.) | ||
+ | * SMTP integration (e.g. sending emails via various services) | ||
+ | * SMS integration (e.g. sending texts via various services) | ||
+ | |||
+ | If you test and discover that something is not working, please open a [[https:// | ||
+ | |||
+ | ===== Feature Testing ===== | ||
+ | |||
+ | VuFind® has a lot of optional features which are not immediately visible. This section of the page provides quick steps for turning on optional features so that you can test and evaluate them. This is intended to be used in combination with VuFind®' | ||
+ | |||
+ | ==== Hierarchical Facets ==== | ||
+ | |||
+ | VuFind® supports indexing data in a specially-formatted way to enable facets to be displayed as a hierarchical tree. The test suite sample data includes a hierarchical facet field which is disabled by default but can be turned on for testing by following these steps: | ||
+ | |||
+ | - In facets.ini, at the top of the [Results] section, add '' | ||
+ | - Also in facets.ini, in the [SpecialFacets] section, add '' | ||
+ | - Now, in the user interface, you should see the facet tree displayed at the top of the sidebar facets in search results | ||
+ | - To test " | ||
+ | - To test "OR facets" | ||
+ | - To test a hierarchical facet on the home screen, add '' | ||
- | ==== Admin Module | + | ==== Library Cards ==== |
- | * Test Statistics | + | VuFind®' |
- | * Does statistics collection enable/ | + | |
- | * Does browser identification work correctly? | + | |
- | * Are record views counted? | + | |
- | * Are searches counted? | + | |
- | * Are no-hit searches counted? | + | |
- | ==== Author Module ==== | + | - In config.ini, in the [Catalog] section, set driver to " |
+ | - In the VuFind® web interface, create a user account (or log in to an existing account). | ||
+ | - On the "Your Account" | ||
+ | - You can now create multiple named library cards with different login credentials; | ||
+ | - Now if you go to the " | ||
+ | - All other features related to the ILS (holds, fines, etc., etc.) should also display the library card selection control. | ||
- | * Test sorting and paging of results. | + | ==== Merging Record Data When IDs Change ==== |
- | ==== Browse Module ==== | + | VuFind® includes a feature to merge locally-stored data like tags and comments when a service reports that a record' |
- | * Test all paths through the browse boxes. | + | When a changed ID is found, an automatic process of reconciling |
- | * Test that result counts are consistent between browse view and search results screen when following links to results. | + | |
- | ==== MyResearch Module ==== | + | Here are step-by-step instructions (examples assume you are running your test environment at http:// |
- | | + | |
- | | + | - Log in to your database on the server |
+ | - Now refresh ''< | ||
+ | - In searches.ini, | ||
+ | - Now go to ''< | ||
+ | | ||
- | ==== Record Module | + | ==== Transaction History |
- | * Test "Cite This" functionality. | + | VuFind® allows users to view (and in some cases purge) their transaction history, but this functionality |
- | * Test "Text This" functionality. | + | |
- | * Test "Email This" functionality. | + | |
- | * Test RefWorks/ | + | |
- | * Test " | + | |
- | ==== Search Module ==== | + | - In config.ini, in the [Catalog] section, set driver to " |
+ | - In Demo.ini, in the [TransactionHistory] section, set enabled to true. | ||
+ | - After creating an account and logging in, a new option should now be available in the account side menu to allow access to transaction history. The Demo driver will populate this with simulated data (and you can log out and back in again to generate a new set of simulated data). | ||
- | * Test sorting and paging of results. | ||
- | * Test that all special searches (author, title, etc.) are actually searching the correct set of index fields. | ||
- | * Test that adding and removing facet filters from the result set works correctly. | ||
- | * Doing an author search should display a box of author facets at the top of the results screen with links to the Author module. | ||
---- struct data ---- | ---- struct data ---- | ||
properties.Page Owner : | properties.Page Owner : | ||
---- | ---- | ||
development/testing/manual_testing.txt · Last modified: 2024/04/08 17:27 by demiankatz