GSTV Quality Assurance Exercise

1. What We Are Looking For
2. Analysis Exercise
   1. Overview
   2. Requirements
3. Technical Exercise
   1. Overview
   2. Installation
   3. Version Control and Submitting

What We Are Looking For

1. Analysis Part - Develop the test plan including test cases and scenarios - including negative paths for the hours functionality that we outlined in the analysis exercise section.
2. Technical Part - We will evaluate your ability to automate tests and your aptitude to learn new technology while doing exploratory testing at the site listed under the technical exercise section.

Analysis Exercise

Overview

The team has built functionality that allows users to create, edit and view hours for a given site. We would like for you to develop the test plan including test cases and scenarios - including negative paths for the hours functionality that we outlined below. It is up to you how you document and organize this information - we just ask that you share your test plan with us prior to your interview.

Requirements

The site - an individual gas station - is one of the lowest-level pieces of the GSTV business model - it is at the core of everything we do. Our hardware is installed at the site, advertisers purchase impressions at a site level and schedules are generated on a per-site basis. Thus, keeping accurate information about a site is essential to maintaining business operations.

This data is used to know when to turn on and off hardware, helps us estimate how many times a video asset is expected to play, and simply is the site open when we try to call them.

A site may have multiple open and close times for a single day. For example, they may be open in the morning, but close mid-afternoon and reopen for the after work rush hour. In many cases stations will be open past midnight, but business owners do not necessarily think of this as the next day.

Taco Bell is a perfect example of business hours vs. chronological hours - they may be open until 4am on Sunday, but you still think of it as Saturday night.

This functionality exists as part of our Site Dashboard application. Every site will have its own page. Each site page will be broken into multiple sections. Each section is called a card. Cards are thematically grouped information - we have cards for site phone numbers, site contacts, and site location information. In this case you will start with an Hours Card.

We have also created wireframes that demonstrate the functionality described in the requirements.

Assumptions

• All times are local times to the site
• We do not take into account Daylight Savings Time
• Authentication and authorization scenarios are not part of this assignment

Card - Hours (View)

• Format
  • Normal State
    • For current date/time
      • Open or Closed
        • Rules
          • If current date and time is within a defined open period, then Open
          • If current date and time is not within a defined open period, then Closed
    • For each day
      • Day Label
        • Full name
      • If not Open 24 hours
        • For each time slot
          • Open Time
          • Close Time
      • If Open 24 hours
        • Message
          • Open 24 hours
      • If Hours are Null
        • Message
          • Closed
    • Edit Site Hours Button
  • Empty State
    • Message
      • There are no site hours for {Site ID}.
    • Create Site Hours Button
• Functionality
  • Edit Site Hours Button
    • Links to Wizard - Hours (Add/Edit/Delete)
  • Create Site Hours Button
    • Links to Wizard - Hours (Add/Edit/Delete)

Wizard - Hours (Add/Edit/Delete)

Create and edit site hours have the same business rules. The main difference is that while editing the dropdowns and values are prepopulated from the server, while in create they are blank.

• Format
  • For each day of the week
    • Day Label
      • Full name
    • Each day may have one or many time slots
    • For each Time Slot
      • Open Time
        • Dropdown
          • Values are in 30 minute increments
          • Values are in AM/PM format
          • Values
            • Start at Midnight and end 11:30 PM
      • Close Time
        • Dropdown
          • Values are in 30 minute increments
          • Values are in AM/PM format
          • Values
            • Start at 12:30 AM and end at 6:00 AM (next day)
            • All values past 11:30 PM (values between Midnight and 6:00 AM) should have the text (next day) at the end
      • Remove Button
    • Open 24 Hours Button
    • Add Button
  • Close Button
  • Submit Button
• Functionality
  • Remove Button
    • Removes the selected time slot
    • If Open 24 Hours
      • Removes Open 24 Hours message
      • Displays one empty time slot
  • Add Button
    • Adds an additional time slot to the selected day
  • Open 24 Hours Button
    • Removes all the time slots if any exist
    • Hides Open 24 Hours Button
    • Message
      • Open 24 Hours
  • Close Button
    • User is returned to the spot where they opened the wizard and the view not reflect any changes
  • Submit Button
    • FE Validates values
      • Null Validation
        • If a start time is entered a close time is required
        • If a close time is entered a start time is required
          • Submit fails
            • Pop Up Message
              • Unable to Create/Update: {itemName} is required.
      • Overlap/Duplicate Validation
        • If a timeslot for a given day overlaps any other time slots on the same day
          • Submit fails
            • Pop Up Message
              • Unable to Create/Update: there is at least one overlapping timeslot
      • Time Slot Format Validation
        • If the start time falls after the end time
          • Pop Up Message
            • Unable to Create/Update: The start time must be before the end time
        • If the end time falls before the start time
          • Pop Up Message
            • Unable to Create/Update: The start time must be before the end time
        • If the start time falls on the end time
          • Pop Up Message
            • Unable to Create/Update: The start time may not be the same date as the end time
      • If FE validation passes
        • Submit changes to the BE
    • BE validates values
      • Null Validation
        • If any required items are null
          • Submit fails
            • Pop Up Message
              • Unable to Create/Update: {itemName} is required.
      • Unchanged Data Validation
        • If any required items are null
          • Submit fails
            • Pop Up Message
              • Unable to Update: {itemName} {itemValue} has not been changed.
      • Duplicate Validation
        • If any required items are null
          • Submit fails
            • Pop Up Message
              • Unable to Create/Update: {itemName} {itemValue} already exists.
      • Malformed Data Validation
        • If any required items are null
          • Submit fails
            • Pop Up Message
              • Unable to Create/Update: {itemName} {itemValue} does not match the expected format.
      • Time Slot Format Validation
        • If the start time falls after the end time
          • Pop Up Message
            • Unable to Create/Update: The start time must be before the end time
        • If the end time falls before the start time
          • Pop Up Message
            • Unable to Create/Update: The start time must be before the end time
        • If the start time falls on the end time
          • Pop Up Message
            • Unable to Create/Update: The start time may not be the same date as the end time
        • If BE validation passes
          • Pop Up Update Data
            • User is returned to the spot where they opened the wizard and the view will reflect changes from the wizard.

Technical Exercise

Overview

We will evaluate your ability to automate tests and your aptitude to learn new technology while doing exploratory testing. Every day visitors reach out to us on gstv.com. We would like your help automating the regression tests for the contact form you can find in our test environment. You should focus on testing both positive and negative test scenarios. We have provided you a solid start on a positive example.

Installation

You will be installing packages/software and running test from the command line. Start by downloading a copy of this repository onto your machine.

Install Node

We are assuming that you already have Node installed on your machine. We use Node.js v4.4.0 and npm 3.10.8

If you do not have Node installed already there are a number of tutorials online that can walk you through this.

Get a Selenium Instance Running

This step is not necessary if you already have an instance of Selenium running on your machine.

npm install -g selenium-standalone

Install WebDriverIO

You will be installing the WebDriverIO test runner that is used by CodeceptJS. Run the following command to install.

npm install -g webdriverio

Get the Selenium Instance Running

The first time you run Selenium on you machine you will need to run a separate installation in addition to starting Selenium. Any subsequent times you will only need to run selenium-standalone start. This will start a Selenium instance on your machine.

If you close your terminal the Selenium instance will stop and you will need to run selenium-standalone start again.

This step is not necessary if you already have an instance of Selenium running on your machine. If you already have Selenium installed make sure to start up the instance before running your tests.

selenium-standalone install
selenium-standalone start

Install CodeceptJS

Codecept JS provides a level of abstraction on top of WebDriverIO and other test runner libraries. We chose CodeceptJS for this exercise because we feel that the test is much clearer than Mocha assertions. Run the following command to install.

npm install -g codeceptjs

Install Project Specific Dependencies

Change directories to the quality-assurance-exercise folder and run npm install.

We have included Faker to generate contextual test data. The documentation outlines how to specify the kind of test data you would like.

Verify Everything Is Working Together

Run npm test or codeceptjs run --steps.

You should see the following shortly afterwards.

Verify Tests Are Running
• I am on page "/contact"
• I see "Reach the team behind the screens"
✓ OK

Adding Tests

Tests are saved in test/specs/*_test.js. CodeceptJS has a number of WebDriverIO specific functions.

Version Control and Submitting

GitFlow and GithubFlow

We use GitFlow on a daily basis - this allows us to build quality control into our development, QA and deployment process.

We are asking that you use a modified Github Flow - sometimes referred to as a feature branch workflow - methodology instead of GitFlow. Conceptually, GitFlow and Github flow are similar.

Please fork our repository and use a feature branch workflow while developing your functionality. When you are ready to submit your work make a pull request against our repository.