smoke_tests.md

https://jira.library.ucla.edu/browse/URS-388
https://github.com/UCLALibrary/ursus/compare/smoketests
https://github.com/UCLALibrary/ursus/pull/441/files https://en.wikipedia.org/wiki/Software_testing

What is Smoke Testing?

A minimal set of tests that determine whether the deployed build is stable or not.

They are used to catch the high-level functional errors in an application.
If the tests fail, then further testing of the application stops,
and the build is refused for additional testing
until the build passes the smoke test.

The term itself is derived from the electronic industry.
While repairing a hardware component,
if the equipment works with no smoke,
the component is said to have passed the test.

The recommended number of test cases is generally 20 on the low end to around 50 on the high end.

• Does it compile?

• Deploy?

• Does the welcome page load?

• Maybe load a test page which does a query against the database to see that this connection works, too.

• They test major functionality and detect early major issues.

• They demonstrate system stability and conformance to requirements.

• They should ensure the navigation of critical paths perform as expected and don't hamper the functionality.

• The focus should be on core application work flow.

• Pick the test cases from the test suite which cover major functionality of the application

• Check critical functionalities of the program is working fine.

Examples

• Does the program run?
• Does the UI open?
• Does clicking the key functionality do anything?
• Clicking or navigating through many or all screens of an application
• Testing that key functionality, such as signup forms, adding to shopping carts, exporting files, etc. work
• Verifying correct layout and visual correctness

TEST SCENARIOS	DESCRIPTION	TEST STEP	EXPECTED RESULT	ACTUAL RESULT	STATUS
Valid login credentials	Test the login functionality of the web application to ensure that a registered user is allowed to login with username and password	1. Launch the application 2. Navigate the login page 3. Enter valid username 4. Enter valid password 5. Click on login button	Login should be success as expected	Pass
Adding item functionality	Able to add item to the cart	1. Select categories list 2. Add the item to cart	Item should get added to the cart	Item is not getting added to the cart	Fail
Sign out functionality	Check sign out functionality	1. Select sign out button	The user should be able to sign out.	User is not able to sign out	Fail

Execute all the major functionality of modules
User is able to login or not with valid login credentials
After login new user can create or not
User that is created viewed or not

---

Tests for URSUS

Smoke test should be able to be run from a local environment.
They collect expectations for what exists in ursus-production.

• status code

• number of facets > 1 less than 50

• it can tell whether ursus has been indexed as expected (it has more than 6000 items)

• if loaded from Home page we expect there to be at least a couple facets

• it grows over time - (these tests will change over time)

• it has tests for search relevancy that exercise various search features (e.g., AND vs OR testing)

Home Page

• the header links are all displaying as links
• the header links go to the correct urls (https://ursus.library.ucla.edu/catalog?utf8=%E2%9C%93&q=&search_field=all_fields)
• check that the catalog result are over 1 and under 1 million
• click on the search icon be sure you are directed to the correct page
• the featured collections are links
• the featured collection links go to the correct urls
• the collection pages have the correct amount of images
• the correct image appears (the elephants)
• the blurb is correct
• the facets are all displaying as links
• the facet links go to the correct url
• the Footer Links appear and are links
• the Footer links go to the correct urls
• list view: image, tile, date created, resource type, photoggrapher
• gallery view: image, title
• pagination: css class-pagination
• sort by relevance
• All fields; click what are the drop down items

Search Page

• per page: click on 20 are there 20 items on the page

Show Page

• back to search link
• new search link
• Item Overview
  • Title
  • Collection
  • Photographer
  • Date Created
  • Publisher
• Physical Description
  • Medium
  • Extent
  • Dimensions
• Keywords
  • Genre
  • Subjects
  • Location
• Find This Item
  • ARK
  • Repository
• Access Condition
  • Copyright Status
  • Rights Country
  • Rights Holder
  • License

Possible Tests for CALIFORNICA

• Login

• Logout

• Are the facets are all displaying as links?

• Do the facet links go to the correct url?