GlyGen Detailed Testing Instructions

GlyGen detailed testing is more comprehensive and intensive than the Quick Testing. The detailed testing not only includes data issues but also interface, display and content issues. In detailed testing GlyGen search, list and details, data, API and SPARQL pages are tested including the search pages. Below are bullet points that help in doing a detail test. The detail test is done primarily on beta and prd interfaces or told otherwise. See the GlyGen subdomains document if you don’t know the subdomain interface you are asked to test. To access GlyGen Tst and Dev servers from your personal PC and or laptop, connect to GW VPN. Download VPN - https://it.gwu.edu/virtual-private-network-vpn | Instructions - 
Create the testing report by giving an appropriate name that contains data, version , tester’s name etc and upload to the recommended location.

GlyGen Search and Advanced Pages -> Explore (https://glygen.org/))
Data page - https://data.glygen.org/
API - https://api.data.glygen.org/
SPARQL – or https://sparql.glygen.org/
To test DEV and TST server, replace $server with the server name here - https://$server.glygen.org/

To do detail testing CHECK

•	Protein, Glycan and Glycoprotein Simple Search Page (All searches, text and links)
•	Protein, Glycan and Glycoprotein Simple Search Page (All searches, text and links)
•	List pages (Links, pages, download)
•	Protein and Glycan detail pages (All data sections and links)
•	Data Page (Datasets, downloads, BCOs, FAQs, Release History)
•	API Page (All APIs, Links)
•	SPARQL Page (All Queries and Links)

Simple Searches
•	To test, search the protein, glycoprotein and glycan simple search pages by using all the searches and examples shown on the interface.
•	Use different search examples from the dataset to test more.
•	Check for the error or issue in the respective API. 
•	Report any issues/errors if the search field generates error when searching by the displayed example.

Advanced Searches
•	To test, search the Advanced Search pages of Glycans, Protein and Glycoprotein using the examples shown on the interface including the examples in the drop down or the sliders.
•	Use different search examples from the dataset to test more.
•	In advanced search pages, some fields allows to use valid combinations to get results. For eg searching of Human proteins that a particular pathway of GO ID. Search using combinations.
•	Enter multiple accessions in search fields where applicable, to test the functionality eg UniProtKB Ac in Protein Advanced search. 
•	Ensure all examples on the advanced search pages are working
•	Check whether the help links are active and working
•	Check whether the info displayed in the help text is correct and uptodate.
•	Report any issues or errors found

List Page

•	To test list pages search using the simple and advanced search pages of protein, glycoprotein and glycan examples.
•	Upon successful searching in the search pages, list page appears that contains the summary of the search, number of search results and tables containing either protein or glycan accessions.
•	Check whether the search summary is correct and as per the search executed, the table contains the correct information, prev and next page options work and the list page can be downloaded.
•	Check whether the downloaded file contains all information shown in the list page
•	Check and see whether the same info is also shown in the API and dataset or when there is an error for verification
•	Make sure to check both glycan and protein list page.

Detail Page
•	Check all the links are working and correct for all sections of protein and glycan detail all pages. Eg UniProtKB ac link should open the UniProtKB page for that accession.
•	Check whether the data displayed is correct. Eg If glycan in N-glycan, then the image should be of N-glycan
•	If the data has error check the data in the APIs and relevant datasets 
•	Check header, footer and menu links and functionality.
•	For some accessions not all sections will have data. Check to ensure there is genuinely no information available for that section. 
•	Ensure the data, page and sections are displayed optimally.
•	Report errors/issues

Data Page
•	Check whether all datasets have images/tables displayed
•	Check whether the filters work on not
•	Click on several datasets to ensure they have sample view page
•	Check description and sample table is displayed on the sample view page
•	Check that datasets can be toggled to different version when the option is available
•	Check BCOs and readme links display the content.
•	Check the download datasets options words and shows all the entries.
•	Check the other menu links such as FAQs, Release history
•	Check the API, SPARQL and Portal links work or not
•	Report any issues/errors

API Page
•	Check whether all APIs can be successfully executed by using the given examples
•	Check if the data displayed is correct and as per the API
•	SPARQL Page
•	Check all the links are working
•	Search the sample queries for result
•	Check if the information is displayed in all the formats

Notes
•	If you find issues, double check the issues
•	Check the data issues in same server API and datasets in dev server before reporting. Copy the datasets locally before opening)
•	Check for grammar and types 
•	Report all issues in a document with as much details as possible (server, browser, data, page, version, URL (most important), screenshots etc)
•	Mention the version, server, date and name etc in the details.

