Test plan for test systems and data

This page collects function tests that should be performed after deploying new software versions (frontend and/or drupal) and after loading data for uniform quality assurance.

0. General

Responsiveness

Check pages for correctness in desktop view and mobile view (affects all pages)

Currently, it should only check it in the Journal Overview Page /content/journal

Localization

Switch between German/English works --> localization (also affects all pages), i.e. pages are also displayed correctly in English, all the path should be in German.

Software tests

Click path

• All menu and submenu items (upper navigation) work, in particular

  • Journal Content ( everything that has in the path /content)

  • {cms url}/sitemap.xml
    
    • i.e. Q systems: https://cms-q1.deutsche-digitale-bibliothek.de/sitemap.xml
• All block links (sidebar content links) should works.
• Each link in the content should work, including links to documents, PDF, ZIP files, ...
  • PDF example you can find it here /content/downloads
  • ZIP example: /content/journal/aktuell/deutsche-digitale-bibliothek-praesentiert-erste-vollversion and /journal/hintergrund/die-bilder-der-digitalisierung-der-vergangenheit-eine-zukunft-kulturelles-erbe-der-digitalen-welt
• If finding a relative URL that doesn't start with /content, those links will not work in DDB Journal but in Frontend. If we have a context path like /ddb-master those relatives URLs will not work either, see DDBNEXT-2869
• All the URLs path should be in German

Start Page

• Main Menu available?
• Footer Menu available?

• Teasers Articles available?

Events /content/ueber-uns/termine

Facets: 

• If a facet is selected, a new search is started, and it will have the number of items that the facet said that it would have and the facets items number should be updated with the new result.
• If the language is changed the page facet/pagination will be reset

Pagination should work as expected and it will appear only if there are more than 10 items.

Calendar Selection works and the days where some event occurs should be highlighted.

If the start or end hour of an event is 00:00 the time should not be shown instead "all-day" should be shown.

Journal Overview Page /content/journal

Max 3 columns and 5 rows in the center content in the page and space for the right sidebar also when there is not content in the right sidebar.

Check responsiveness follow what is described in 

Exhibition List Page /content/journal/ausstellungen

Each item article should have: 

• a picture
•  title and a short description
• To the exhibition

The image, title and "To the exhibition" links should link to the exhibition external page and it should open in the same page. (Existing issue  ) 

From v7.0 infinite scrolling has been implemented  on this page.

Therefore pagination should be performed automatically and work when scrolled to the bottom of the page.

Archive Page /content/journal/archiv

Facets: 

• If a facet is selected, a new search is started, and it will have the number of items that the facet said that it would have and the facets items number should be updated with the new result.
• If the language is changed the page facet/pagination will be reset

Each item article should have:

• a picture
• a date
•  title and a short description. 

The title and the picture should be also a link that will connect to the detail page of the article.

Pagination should work as expected and it will appear only if there are more than 20 items. 

Category Article List Pages 

•  News /content/journal/aktuell  
• Discover /content/journal/entdecken 
• Background /content/journal/hintergrund

Each item article should have:

• a picture
• a date
•  title and a short description
• Read more link

The title, read more and the picture should be also a link that will connect to the detail page of the article.

The three pages should have the same design as the Exhibition Page.

Pagination should work as expected and it will appear only if there are more than 10 items.

On this day page, From the collections page

Because the DI master frontend is configured to use the backend in DI but Elastic Search in Q it is possible that objects and their images cannot be found in favorites lists. In this case the title "Object no longer available" occurs.

Browser Compatibility

Test requirements

Systems