Software Testing

Instructor: Chris Fulton

Learning Objectives

• Software Testing
• Why is software testing important?
• System Development Life Cycle(SDLC)
• Functional vs. Non-Functional Testing
• Types of Test
• Unit Testing Node.js - Using Jest Testing Framework
• Integration Testing
• End to End Tests
• UI Tests
• Software Automation Tools
• Selenium
• Webdriver.io

Why is software testing important?

Understanding SDLC

What do we test and how do we know what to test? We start with the system development life cycle (SDLC). This SDLC informs us on what we are going to test and what are critical requirements defined by the client.

SDLC Process and responsibility

SDCL Brief Overview

Functional vs. Non-Functional Test

A number of functional and non-functional test can be completed using tools that allow for automation vs. manually testing even non-functional test.

Unit Testing

Node.js Unit Testing Frameworks

Node.js Testing Frameworks - Some are opininated and some are catered toward other frameworks.
Stateofjs.com testing framework rankings

Crafting a Unit Test

The purpose of the test to ensure that the unit of code is properly functioning as intended. Some would encourage test-driven development to enforce compliance.

Crafting a Unit Test Example

Simple Arithmetic function that adds two numbers together and returns sum

Unit Test Activity 1

①
									
npm init
									
								

②
									
npm install --save-dev jest
									
								

③
									
{
  "scripts": {
    "test": "jest"
  }
}
									
								

④
									
function sum(a, b) {
  return a + b;
}
module.exports = {sum};
									
								

⑤
									
const sumModule = require('./sum.js');

var total = sumModule.sum(2,3);
console.log(total);
									
								

⑥
									
const sum = require('./sum');

test('adds 1 + 2 to equal 3', () => {
  expect(sum.sum(1, 2)).toBe(3);
});
									
								

Activity 2

For this activity, please refer to the previous slide on project structure

						
							function getFavoriteNum(favNum){
							    var enteredNum = favNum;
							    return favNum;
							}
							
							module.exports = {getFavoriteNum};
						
					

Integration Testing

What is Integration Testing

Integration tests determine if independently developed units of software work correctly when they are connected to each other. More often than not, the focuses is on the flow of data between modules

Overview of Integration Testing

Resource from guru99

Integration Testing Process

1. Prepare the test integration plan. Sample Integration Test Plan

2. Decide on the type of integration testing approach

3. Design test cases, test scenarios and test scripts accordingly.
A test case is a document which has a set of conditions or actions that are performed on the software application in order to verify the expected functionality of the feature.

4. Deploy the chosen modules together and get the integration tests running

5. Track the defects and record the test results of tests

6. Repeat the above steps until the complete system is tested

Types of Integration Testing

End-to-End Testing

End-to-End Testing Frameworks

End-to-End Testing test an application flow from start to end. The purpose of End to end testing is to simulate the real user scenario and validate the system under test and its components for integration and data integrity. The purpose of end-to-end Test is to exercise a complete production-like scenario. Focuses on simulation and interface interaction.

References

• https://medium.com/@nathankpeck/microservice-testing-unit-tests-d795194fe14e
• https://www.edureka.co/blog/what-is-integration-testing-a-simple-guide-on-how-to-perform-integration-testing/