Difference between revisions of "Development/Functional testing"
m (Fix link) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
[[Main Page]] > [[Development]] > Development/Functional testing | [[Main Page]] > [[Development]] > Development/Functional testing | ||
| + | To help prepare for releases, Artefactual analysts regularly perform manual end-user functional tests of the application, to identify and resolve bugs and regressions prior to a release. The following pages cover some of the manual functional tests performed during the release process via the user interface by end users. | ||
Functional testing starts with a list of steps which must be completed to verify that specific modules and/or features are working in AtoM. These lists can be used for manual testing, for creating automated functional tests, or for updating automating functional tests when/if the application/interface changes. | Functional testing starts with a list of steps which must be completed to verify that specific modules and/or features are working in AtoM. These lists can be used for manual testing, for creating automated functional tests, or for updating automating functional tests when/if the application/interface changes. | ||
| Line 17: | Line 18: | ||
Please remember to search in Redmine for your issue before creating a new one - thanks! If you are uncertain about whether or not you have encountered a bug, you are welcome to make a post to our [https://groups.google.com/forum/#!forum/ica-atom-users User forum]. | Please remember to search in Redmine for your issue before creating a new one - thanks! If you are uncertain about whether or not you have encountered a bug, you are welcome to make a post to our [https://groups.google.com/forum/#!forum/ica-atom-users User forum]. | ||
| + | |||
| + | <admonition type="seelaso"> | ||
| + | For automated tests useful in development, see: | ||
| + | |||
| + | * [[Development/Testing|Testing]] | ||
| + | |||
| + | </admonition> | ||
---- | ---- | ||
| Line 43: | Line 51: | ||
*[[Development/Functional testing/User accounts tests]] | *[[Development/Functional testing/User accounts tests]] | ||
*[[Development/Functional testing/Validation tests]] | *[[Development/Functional testing/Validation tests]] | ||
| + | |||
| + | ------ | ||
| + | |||
| + | * [[Development|Back to Development]] | ||
| + | * [[Main Page|AtoM wiki home]] | ||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Latest revision as of 07:55, 6 April 2021
Main Page > Development > Development/Functional testing
To help prepare for releases, Artefactual analysts regularly perform manual end-user functional tests of the application, to identify and resolve bugs and regressions prior to a release. The following pages cover some of the manual functional tests performed during the release process via the user interface by end users.
Functional testing starts with a list of steps which must be completed to verify that specific modules and/or features are working in AtoM. These lists can be used for manual testing, for creating automated functional tests, or for updating automating functional tests when/if the application/interface changes.
This document was created at the time of AtoM 2.0.1, just prior to the AtoM 2.1 release. As such, it will begin by documenting AtoM 2.1 functional tests. If you are trying to perform functional testing on an earlier version of AtoM or ICA-AtoM, we recommend consulting the User Manual for each to verify where functionality is different. For each major release, we will be versioning the AtoM 2 documentation, so previous version can remain available:
- AtoM 2 documentation: https://www.accesstomemory.org/docs/
- ICA-AtoM documentation: https://www.ica-atom.org/doc/User_manual
For future versions of AtoM (e.g. 2.2, etc.), we will add a version-specific note to the existing functional testing docs where relevant.
If you are performing tests and encounter a bug, please let us know! We use Redmine as our issue ticketing system. Information on its use, and how we prefer that bugs be filed, can be found here: Resources/Issue tracker.
Please remember to search in Redmine for your issue before creating a new one - thanks! If you are uncertain about whether or not you have encountered a bug, you are welcome to make a post to our User forum.
- Development/Functional testing/Access control tests
- Development/Functional testing/Accession module tests
- Development/Functional testing/Actor object tests (aka Authority record tests)
- Development/Functional testing/Admin tests
- Development/Functional testing/Browse tests
- Development/Functional testing/Deaccession module tests
- Development/Functional testing/Digital object tests
- Development/Functional testing/Export/import tests
- Development/Functional testing/Function tests
- Development/Functional testing/Information object tests
- Development/Functional testing/Physical Storage tests
- Development/Functional testing/Repository object tests
- Development/Functional testing/Rights module tests
- Development/Functional testing/Search tests
- Development/Functional testing/Single sign-on (CAS) tests
- Development/Functional testing/Taxonomies tests
- Development/Functional testing/Translation tests
- Development/Functional testing/Treeview hierarchy tests
- Development/Functional testing/User accounts tests
- Development/Functional testing/Validation tests