Prepare
Practice
Interview
Aptitude
Reasoning
English
GD
Placement papers
HR
Current affairs
Engineering
MCA
MBA
Online test
Login
Debugging is not Testing, but always occurs as consequences of testing - Software Project Planning
Home
>>
Category
>>
Software Testing (MCQ) questions and answers
>>
Software Project Planning
Q. Debugging is not Testing, but always occurs as a consequences of testing.
- Published on 13 Aug 15
a.
True
b.
False
ANSWER: True
Related Content
Incident Management (
7
)
SDLC (
45
)
Agile testing (
9
)
Smoke and Sanity testing (
4
)
Static analysis tools (
6
)
Use cases and Decision table (
4
)
Roles in Software Testing (
5
)
Independent testing team (
6
)
Test processes (
16
)
Structure based testing techniques (
5
)
Risk analysis and management (
20
)
Configuration management (
6
)
Boundary value analysis (
11
)
Testing types and levels (
30
)
Capability maturity model integration (
6
)
Acceptance testing (
7
)
Static testing techniques (
9
)
Basic concepts of Software Testing (
63
)
Software Testing Techniques (
12
)
Software Testing Strategies (
13
)
Software Project Planning (
10
)
Software Design Concept (
13
)
Software Configuration Management (
10
)
Load Runner (
25
)
Manual testing (
58
)
QC (
26
)
QTP (
25
)
Selenium (
26
)
Discussion
Prajakta Pandit
-Posted on 24 Nov 15
- The above statement is true.
- Debugging is not testing, but always occur as a consequences of testing.
- Debugging is an action that results in the detection of error.
- This process begins with the execution of a test case.
➨
Post your comment / Share knowledge
Required!
Required!
Invalid Email Id!
Required!
Enter the code shown above:
Please enter the code shown above
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
MCQs
English
Tutorials
Download
▲
