Skip to content

Commit

Permalink
Junit -> JUnit
Browse files Browse the repository at this point in the history
  • Loading branch information
dentonmwood committed Dec 6, 2019
1 parent ffd5a1b commit a91f57c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Selenium Test Suite

## Overview
The test suite is designed to run End-to-End (E2E) tests on the microservices of the myICPC application. It may easily be extended to all microservices and the main ICPC application (hereafter referred to as the **"monolith"**). The tests are written in Junit, and they use Selenium to scrape the browser output.
The test suite is designed to run End-to-End (E2E) tests on the microservices of the myICPC application. It may easily be extended to all microservices and the main ICPC application (hereafter referred to as the **"monolith"**). The tests are written in JUnit, and they use Selenium to scrape the browser output.

## Technologies Used
- **Junit** - Java testing framework. Runs the tests and supplies input.
- **JUnit** - Java testing framework. Runs the tests and supplies input.
- **Selenium** - Reactive testing framework. Spins up browser instances and collects output. **Selenium Grid** ensures that the tests can be run on multiple browsers. It consists of a Hub and a Node. The Node runs several browser instances which connect to the Hub.
- **Maven** - dependency manager. Packages the tests as a JAR and handles any test dependencies.
- **Docker** - container software. Sticks the JAR in a small Linux container that is independent of the surrounding environment (defined in the Dockerfile). **Docker Compose** spins up containers for all elements of the application (Postgre, Redis, the main myICPC application, the UI, etc.), and runs the tests.
Expand Down

0 comments on commit a91f57c

Please sign in to comment.