Functionality Tests

Question 1

With functionality tests, are we testing multiple components at a time?

Answer 1

No, we test one component at a time

Question 2

What does positive testing involve?

Answer 2

We are testing if a component is working according to the FRD

Question 3

What is another name for positive testing?

Answer 3

Happy path test

Question 4

What does negative testing involve?

Answer 4

• We try to come up with multiple ways a component can fail
• Purposefully causing a failure, to make sure it fails properly

Question 5

What does boundary testing involve?

Answer 5

Validating input range

Question 6

What are the two types of validation under boundary testing?

Answer 6

1. UI level validation
2. DB level validation

Question 7

What is UI level validation?

Answer 7

The app screen won’t even let you move forward without the required fields filled in

ex: Can’t leave login or password field blank on a login screen, leading to an error message

Question 8

What is DB level validation?

Answer 8

Needs a trigger. Database won’t accept input because some input was missing or incorrect

ex: Password field on login screen is filled in, but password is incorrect leading to an error message

Question 9

What does smoke testing involve

Answer 9

• First test run of a new build, to see if the build is stable
• Without any guidance from RD, based on user’s observations, self-navigation

Question 10

What does ADHOC/ Exploratory testing involve?

Answer 10

Identify usability and user-friendliness of the app without having prior knowledge of the app

Question 11

What is functional test?

Answer 11

Will include all the different types of functionality testing, except for smoke test