You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

--draft--draft--draft--draft--draft--draft--draft--draft–draft

Seamless Access uses staging approach for establishing environment for quality assurance of new software versions:

  • staging.build.thiss.io as front-end and md-staging.thiss.io as back-end metadata service - development branch used for development testing
  • build.thiss.io as front-end and md-staging.thiss.io as back-end metadata service - master branch used for QA testing before release to beta
  • use.thiss.io as front-end and md.thiss.io as back-end metadata service - beta service used for testing by SA implementors
  • service.seamlessaccess.org as front-end and md.seamlessaccess.org - production service

Non-functional testing

SUNET NOC and status.seamlessaccess.org performs different non functional testing for beta service and production service as defined in the Seamless Access Monitoring and Reporting 

Functional testing

Functional testing needs to be performed on master branch to determine wether a software version is candidate for release to beta service. Same set of test should be applied to beta service to confirm that the software is ready for release to production. 

---- tbd 

Cases for searching in discovery service: 

  • Special characters: e-science.pl
  • Short names: mit
  • Common names: University of London
  • International names: Enskilda Hogskolan Stockholm, Università degli Studi di Pisa
  • Timing issues when searching longer names with a lot of search results: University


  • No labels