TDD Basic Flashcards

1
Q

What Are The Some Clarifications About Tdd?

A
  • TDD is neither about Testing nor about Design.
  • TDD does not mean write some of the tests, then build a system that passes the tests.
  • TDD does not mean do lots of Testing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What Is Test Driven Development (tdd)?

A
  • designing and developing tests for every small functionality of an application
  • Test is developed which specifies and validates what the code will do.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What Is The Primary Goal/benefit Of Unit Testing?

A
  • Having solid unit tests allows the developers to refactor without fear. That is, they can much more easily maintain and extend the application.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What Are The Benefits Of Tdd?

A
  • Early bug notification
  • Better Designed, cleaner and more extensible code
  • Confidence to Refactor
  • Good for teamwork & Developers since less debugging time and can easily pick up and work on code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What Are Some Of The Common Pitfalls Of Tdd/unit Testing?

A
  • Testing using shared resources is difficult

- Type specific values don’t compare well

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How To Perform Tdd Test?

A
  • Add a test.
  • Run all tests and see if any new test fails.
  • Write some code.
  • Run tests and Refactor code.
  • Repeat.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What Are The Difference Between Tdd Vs. Traditional Testing?

A
  • TDD ensures that your system actually meets requirements defined for it
  • TDD more focus is on production code that verifies whether testing will work properly. In traditional testing, more focus is on test case design.
  • TDD, you achieve 100% coverage test. Every single line of code is tested unlike traditional testing.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Negative Testing

A

test for invalid inputs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Positive Testing

A

test with valid inputs and compare result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Verification

A

check if everything is going according to plan during SDLC

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Validation

A

see if product meets company’s need

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Stress Testing

A

test how the system perform with lack of resource of functional impairments

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Load Testing

A

testing system under normal amount of stress with the expected load

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

QA

A

Quality Assurance - define the way of monitoring and implementing quality of process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

QC

A

Quality Control - process of finding defects and improving

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Testing

A

process to ensure product meet end user requirements

17
Q

Functional Testing

A

test the system function same as requirement

18
Q

Non functional testing

A

test non functional part of the application (e.g. load, stress)

19
Q

Static Testing

A

review documents to identify defects

20
Q

Dynamic testing

A

execute code to validate output with expected outcome

21
Q

White box

A

test functionality with code written (e.g. unit test)

22
Q

Black box

A

test functionality without looking at code

23
Q

Grey box

A

test functionality both with and without looking at code

24
Q

Unit testing

A

check if individual module of the code is working properly

25
Q

Integration testing

A

testing two or more programs that depend on each other

26
Q

System Testing

A

testing fully integrated application to evaluate the system’s compliance with its requirements

27
Q

Acceptance testing

A

done by end user to validate the functionality fo application

28
Q

STLC

A
  • Requirement Analysis
  • Test Planning
  • Develop Test cases
  • Set up environment
  • Execute
  • Cycle closure
29
Q

Data drive automated testing

A

data saved in spreadsheet

30
Q

Keyword Driven Testing

A

Uses data files to contain keywords related to application being tested.

31
Q

Modular Automation

A

script developed based on modules of the application

32
Q

Hybrid Automation

A

use advantage of both keyword and data driven framework

33
Q

Automated Testing Methods

A
  • Unit
  • Integration
  • Black box
  • Functional
34
Q

Manual Testing methods

A
  • Acceptance
  • System Testing
  • Integration testing