問題一覧
1
enable users to plan, organize and track tasks, resources, timelines and deliverables throughout the life cycle
Project Tracking Tools
2
ongoing effort to enhance products, services/processes through incremental and breakthrough improvements
Continuous Improvement
3
applying lessons learned from previous projects to improve oitcomes
Continuous Improvement
4
KPIs stands for?
Key Performance Indicators
5
quantifiable measure of performance overtime for a specific objective
KPIs
6
provides targets for teams to shoot for
KPIs
7
used by individuals and organizations to evaluate their success at reaching critical tagets
KPIs
8
use these when you need to track process towards a goal over a specific period of time
KPIs
9
measurable value that demonstrates how effectively a company is achieving key business objectives
KPIs
10
a quantifiable measure used to track and assess the status of a specific process
Metrics
11
in data context, these are numbers/values that can be summed/averages
Measures
12
clear and concise framework that embraces every element of the operations on an organization not least QUALITY MANAGEMENT (fosters culture of constant, ongoing improvements)
Quality Assurance
13
specifications/styles that are widely accepted by users and adopted by several vendors
Standards
14
critical to the compatibility of hardware, software or anything in between
Standards
15
enable essential elements of a computer and related infrastructure to work together
(Industry) Standards
16
internally agreed set of standards for software testing that can be used within any software development life cycle
Software Testing Standards
17
by implementing these, you will be adopting the only internationally-recognized and agreed standards for software testing, providing high-quality approach to testing of your organization
ISO/IEC/IEEE 29119
18
ISO/IEC-1,2,3,4,5
Concepts and Definitions, Test Processes, Test Documentation, Test Techniques, Keyword Driven Testing
19
titled "Systems and software engineering-Software and System Quality Requirements and Evaluation(SQuaRE) -system6and software quality models
ISO 25010
20
quality in use model composed of characteristics that relate to the outcome of interaction when a peodu6is used in a particular context of use
ISO 25010
21
globally recognized standard for quality management systems(QMS)
ISO 9001
22
while not specific to software development, the key principles of this can help software organizations improve their processes, etc.
ISO 9001
23
MISTAKE for C/C++
Code Quality Standards
24
makes sure the code is clean and safe
Code Quality Standards
25
provides framework for test documentation
IEEE 829
26
rules to make sure software protectsuser data and follows laws
Compliance Standards
27
involves human testers interacting with the software under test to identify defects and ensure functionality
Manual Testing
28
has a vital role in uncovering issues in areas like human judgement and intuition
Manual Testing
29
Examples of Manual Testing(4)
Exploratory Testing, Black Box Testing, White Box Testing, Grey Box Testing
30
dynamic and flexible approach where testers are encouraged to explore the software freely
Exploratory Testing
31
emphasizes learning and adaptation, allowing testers to adjust their testing strategies based on observations and/or insights
Exploratory Testing
32
focuses on external behavior of the software without considering it's internal structure/code
Black Box Testing
33
involves examining the software's internal structure and code to verify it's logic, flow and implementation
White Box Testing
34
testers have access to the source code and use their knowledge to programming languages to design test codes
White Box Testing
35
testers have some knowledge of the software's internal structure and code, but don't have full access to the source code
Grey Box Testing
36
use their knowledge on specific areas of the software
Grey Box Testing
37
utilize specialized tools to execute test cases automatically, reducing the need for manual intervention and accelerating test processes
Automated Testing
38
effective for repetitive tasks, regression and performance testing
Automated Testing
39
Examples of Automated Testing
Selenium, J Unit Test NG, Test NG
40
widely-used open-source framework for automating web browser interactions
Selenium
41
allows testers to create scripts like clicking buttons, filling forms and navigating web pages to simulate user actions
Selenium
42
provides an approach for writing and executing unit tests
J Unit Test NG
43
powerful testing framework for Java, designed to simplify and enhance the process of writing and running tests
Test NG
44
fundamental practice in software development, focusing on testing individual code units in isolation
Unit Testing
45
aims to verify that each unit of code performs it's intended function correctly and meets specific requirements
Unit Testing
46
focuses on verifying the interactions and interfaces between integrated components/systems
Integration Testing
47
comprehensive testing phase that evaluates the entire integrated software application
System Testing
48
type of software testing that ensures recent code changes does not affect the existing functionality
Regression Testing
49
evaluate how a system behaves and performs under various conditions
Performance Testing
50
primary goal:to ensure software applications meet certain performance criteria (speed, responsiveness, scalability, stability)
Performance Testing
51
crucial for identifying potential bottlenecks and ensures a system can handle expected traffic/usage levels
Performance Testing
52
Examples of Performance Testing
Load Testing, Stress Testing
53
how system performs under normal and peak load conditions
Load Testing
54
helps identify the maximum operating capacity of an application
Load Testing
55
pushing the system beyond its limits to identify the breaking point and how it recovers from the failure
Stress Testing
56
process of evaluating a system/application to ensure that it's secure from potential threats, vulnerabiliry and risks that could lead to unauthorized access, data breaches or system malfunctions
Security Testing Quality Assurance
57
Examples of Security Testing
Penetration Testing, Fuzz Testing
58
simulates real-world attacks on a system to identify security weaknesses
Penetration Testing
59
often performed manually/with automated tools
Penetration Testing
60
sends random/unexpected data to a system to identify potential vulnerabilities like buffer overflows, crashes or data leaks
Fuzz Testing
61
developers write tests before coding
TDD
62
ensures the code is reliable and meets requirements
TDD
63
collaboration between developers, testers and stakeholders
BDD
64
helps create automated tests based on user-expectations-ensuring final product meets requirements
BDD
65
design based on user needs and feedback
UCD
66
helps tailor solutions to real user problems
UCD
67
observe real users interacting with the software to spot issues
Usability Testing
68
identifies pain points and improve usability
Usability Testing
69
experts review the interface using established usability principles
Heuristic Evaluation
70
evaluates consistency, feedback and error prevention
Heuristic Evaluation
71
ensure the software is usable for people with disabilities
Accessibility Testing
72
compares 2 product versions with users
A/B Testing
73
improves decision-making with real user input
A/B Testing
74
gather feedback from user groups
Focus Groups
75
provides insight to iser needs and perspectives
Focus Groups
76
key step in software testing where real users try out the software in real-life situations
UAT
77
confirm everything is functional
UAT
78
final testing phase performed by end-users to validates thta the system meets their needs
UAT
79
performed in-house by the development team and internal testers(including quality assurance staff)
Alpha Testing
80
one of the 1st phases of testing aimed at identifying bugs and issues early in the development process
Alpha Testing
81
releasing the software to a selected group of real users outside the organization
Beta Testing
82
goal:identify remaining bugs, usability issues and improvements needed
Beta Testing
83
systems are developed according to the agreed-upon requirements and protects both the client and provider
Contractual Testing
84
tests only the parts of the provider's behavior that the consumer actually uses
Consumer-Driven Contract Testing
85
provider tests that it's system behaves according to the contract
Provider-Driven Contract Testing
86
test that demonstrates correct operation of system's functions as specified within the contract
FAT
87
for newly manufactured system
FAT
88
purpose:ensure that the machine/system meets the requirements that were ordered by the customer
FAT
89
conditions that must be met for formal project approval
Sign Off Criteria
90
ensuring legal and regulatory adherence
Compliance Audits
91
ensure compliance with relevant laws, regulations and standards
Compliance Audits
92
prevents legal issues and potential fines
Compliance Audits
93
maintains public trust
Compliance Audits
94
product operates within legal boundaries
Compliance Audits