Software Testing Methodologies

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/34

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

35 Terms

1
New cards

Manual Testing

Manual inspection of the software by a human tester

2
New cards

Automated Testing

Uses software tools to automate testing process

3
New cards

Functional Testing

Verifies that the functions of the software application works in conformance with the requirements

4
New cards

Non-functional Testing

Deals with how well the software operates rather than verifying the outcome of software functions

5
New cards

Unit Testing

Tests individual units or components of the code/software

6
New cards

Integration Testing

Tests how different components of the software interacts to ensure they work together as a system

7
New cards

System Testing

Tests the complete software system to ensure it meets specified requirements

8
New cards

Acceptance Testing

Tests to make sure the software meets customer’s or end-user’s expectations

9
New cards

Regression Testing

Re-executing a previously created test suite to verify that changes to the code did not cause new problems

10
New cards

Performance Testing

Tests the software to determine performance characteristics such as speed, scalability, and stability

11
New cards

Security Testing

Tests the software to identify vulnerabilities and ensure it meets security requirements

12
New cards

Exploratory Testing

The tester actively explores the software to find defects without following a specific test plan

13
New cards

End-to-End

Testing that replicates a user’s behavior with the software in a complete application environment

14
New cards

Boundary Value Testing

Edge case testing

15
New cards

Usability Testing

Tests the user-friendliness and ease of the software

16
New cards

Smoke Testing

Basic tests that check basic functionality of an application

17
New cards

Automated testing helps speed up []

Continuous Delivery (CD)

18
New cards

Auto testing is an [] process of a [] process

Automation, manual

19
New cards

Auto testing is used to automate [] [] that are difficult to perform manually

testing tasks

20
New cards

Automation tests can be ran at []

anytime of the day

21
New cards

Reasons for using automation testing

Quality Assurance, Error or Bug-free software, No human intervention, Increased test coverage, and Frequent testing

22
New cards

What kinds of software tests should be automated first?

End-to-end tests, unit tests, integration tests, and performance tests

23
New cards

Most common automation frameworks

Linear framework, modular-based framework, and library architecture framework

24
New cards

Automation Testing Process

Select test tool, define automation scope, plan design develop, test execution, and maintenance

25
New cards

“Reassessing the [] as the app develops and changes” is a best practice for Software Automation

test plan

26
New cards

“Plan for [] test cases” is a best practice for Test Automation

Self-contained

27
New cards

“Planning [] execution” is a best practice for Test Automation

test order

28
New cards

“Use tools with [] scheduling” is a best practice for Test Automation

auto

29
New cards

“Set an [] for test failure” is a best practice for Test Automation

alarm

30
New cards

M__ tests should be automated

Monotonous

31
New cards

Tests with multiple [] should be automated

Data sets

32
New cards

Business [] tests should be automated

Critical

33
New cards

D__ tests should be automated

Determinant

34
New cards

What is a Determinant test case?

Test case where it is easy for the computer to decode whether the test has failed or can be automated

35
New cards

T__ tests should be automated

Tedious