Skip to content

Commit

Permalink
typo
Browse files Browse the repository at this point in the history
  • Loading branch information
RichardBruskiewich committed Sep 14, 2023
1 parent 4abe7d5 commit 8313fc1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/guide-for-developers/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
The Translator project is first and foremost, an initiative to create a novel complex software system to process biomedical knowledge. Testing of such software may be envisioned and implemented at several distinct levels:

* **[Unit Tests](#unit-testing):** code testing harnesses of granular tests embedded within a given project using well understood "best practices" applied in a computer language specific manner.
* **[Continuous integration / dev ops Testing](#continuous-integration-testing):** as distinct components of a complex multi-component system are deployed into a common environment to run as an integrated system, unit and component integration tests may be run automatically to assess compatibility and function of the software component codee and its dependencies with the context of the common environment.
* **[Continuous integration / dev ops Testing](#continuous-integration-testing):** as distinct components of a complex multi-component system are deployed into a common environment to run as an integrated system, unit and component integration tests may be run automatically to assess compatibility and function of the software component code and its dependencies within the context of the common environment.
* **[System-level Testing](#system-level-testing):** Translator has evolved into a loosely-coupled web services-integrated system with shared communication syntax/semantics (i.e. TRAPI) and semantics (Biolink Model) standards for interoperability. System level testing validates component compliance with such interoperability standards.
* **[User Interface Testing](#user-interface-testing):** a software system is only ultimately as useful as the quality, fitness-of-purpose and performance of the human-machine interface. User experience testing and related methodology achieves such testing objectives.
* **[Quality Assurance Testing](#quality-assurance-testing):** again, with Translator, which is a biomedical (scientific) knowledge navigation, integration and interpretation system, "quality" refers to the scientific completeness, precision and credibility of the semantically encoded results. Tests for "Quality Assurance" may be devised to the query request/response of the system
Expand Down

0 comments on commit 8313fc1

Please sign in to comment.