Software Testing Types and Methods

• Software testing is a phase in software engineering

Types of Testing

• Functional testing makes sure the components of software function according to specifications.
• Performance testing: assesses the speed, stability, and scalability of a system or application under various workloads.
• Cybersecurity testing assesses the security flaws, threats, risks in a software application, and prevents malicious attacks.
• Usability testing evaluates how easy a design is to use on a group of representative users.

Methods of Testing

• Black box testing evaluates the functionality of a software application without knowledge of the internal code structure or implementation
• White box testing validates internal structures and code and is performed by developers.

Black Box Testing

• Is performed with no knowledge of a system's internal workings
• It evaluates functionality, security, performance, and other aspects of an application.
• It examines the functionality of an application without peering into its code.
• Testers input data and observe the output to check how the system responds to expected and unexpected actions, speed, usability, and reliability.
• It enhances software's reliability, user experience, and quality

Black Box Testing Scenarios

• For testing functional requirements
• For user acceptance testing (UAT)
• For regression testing
• When performing load and performance testing
• For usability testing
• To ensure security
• To validate output
• For integration testing

Features of Black Box Testing

• Functional testing verifies login capability using correct user credentials and inability to login using incorrect credentials
• Non-Functional testing checks usability, performance under expected or peak loads, compatibility, and exposure to security vulnerabilities

Black Box Regression Testing

• Used to check if a new version of the software exhibits a regression or faults in capabilities from one version to the next
• It can be applied to functional or non-functional aspects of the software

Black Box Test Cases

• Testers creates a positive test scenario with valid inputs
• Testers creates an adverse test scenario with invalid inputs
• The software is checked that it is processing correctly or incorrectly.

Use Case Testing

• Use Case Testing validates the functionality of a system according to user interactions.
• Steps for the example "Log in" Use Case
  • Enter username
  • Enter password
  • A successful outcome will return "Log in successful, user see first page of the application"

Black Box Testing Example: Online Shopping Application

• A login functionality can use black box testing
• It tests the login page without having access to the internal code or implementation details.
• Test Case Name: Verify successful login with valid credentials.
• Test Steps:
  • Open browser
  • Enter URL of the application's login page
  • Enter a valid username in the username field
  • Enter a valid password in the password field
  • Click the "Login" button
  • Wait for the application to process the login request
• Expected Result: User should be successfully logged into the application's homepage.
• Test Case Status: PASS (if the user is redirected to the homepage)

Black Box Testing Example: Unsuccessful Login

• Test Case Name: Verify unsuccessful login with invalid credentials.
• Test Steps:
  • Open browser
  • Enter URL of the application's login page
  • Enter an invalid username
  • Enter an invalid password
  • Click "Login" button
  • Wait for the application to process the login request
• Expected Result: The login attempt should fail and an error message should be displayed on the login page.
• Test Case Status: PASS (if the error message is displayed)

Online Shopping Application "Purchase Item" Use Case

• Steps:
  • Select item
  • Add to cart
  • Proceed to checkout
  • Enter payment details
  • Confirm purchase
• Expected Outcome: Order confirmation is displayed, and order is recorded.