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 revision | ||
development:testing:manual_testing [2023/04/12 16:43] – removed - external edit (Unknown date) 127.0.0.1 | development:testing:manual_testing [2024/04/08 17:27] (current) – demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Manual Testing ====== | ||
+ | |||
+ | VuFind® uses a set of [[development: | ||
+ | |||
+ | ===== General Considerations ===== | ||
+ | |||
+ | ==== Browser Testing ==== | ||
+ | |||
+ | It is a good idea to test the interface in multiple browsers to check for display inconsistencies and Javascript incompatibilities. | ||
+ | |||
+ | * Firefox | ||
+ | * Edge | ||
+ | * Chrome | ||
+ | * 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 ==== | ||
+ | |||
+ | Some general patterns to follow when testing new features: | ||
+ | |||
+ | * Test fields stored in the database for SQL injection vulnerabilities. | ||
+ | * Test fields sent as Solr searches for vulnerability to syntax errors. | ||
+ | * Test fields where input is stored and displayed back for XSS vulnerabilities and missing HTML/URL encoding. | ||
+ | |||
+ | 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®' | ||
+ | |||
+ | ==== Combined Search ==== | ||
+ | |||
+ | If you want to test [[configuration: | ||
+ | |||
+ | ==== 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 '' | ||
+ | |||
+ | ==== Library Cards ==== | ||
+ | |||
+ | VuFind®' | ||
+ | |||
+ | - 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. | ||
+ | |||
+ | ==== Merging Record Data When IDs Change ==== | ||
+ | |||
+ | VuFind® includes a feature to merge locally-stored data like tags and comments when a service reports that a record' | ||
+ | |||
+ | When a changed ID is found, an automatic process of reconciling and deduplicating saved data occurs. These steps, combined with data in the default test data, can allow you to confirm that this process works correctly. | ||
+ | |||
+ | Here are step-by-step instructions (examples assume you are running your test environment at http:// | ||
+ | |||
+ | - Go to ''< | ||
+ | - Log in to your database on the server and run '' | ||
+ | - Now refresh ''< | ||
+ | - In searches.ini, | ||
+ | - Now go to ''< | ||
+ | - Now you can check that everything merged together correctly -- all of the tags, favorites, comments and notes you created in steps 1 and 3 should be combined together in the record view. | ||
+ | |||
+ | ==== Transaction History ==== | ||
+ | |||
+ | VuFind® allows users to view (and in some cases purge) their transaction history, but this functionality is disabled by default. To see how it behaves, follow these steps: | ||
+ | |||
+ | - 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). | ||
+ | |||
+ | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
+ | ---- | ||