Bottom Up Approach:

The bottom up approach testing approach is carried out with the help of the test driver. The test driver calls a component to be tested.

The modules in the lower level of call hierarchy are tested independently. Then the next level modules are tested that call previously tested modules. This is done repeatedly until all the modules are included in the testing.

Bottom up testing stops when the top module in the call hierarchy is tested with all lower call hierarchy modules.

Top Down Approach:

The top down approach is carried out with the help of the test stub. Test stub are the dummy programs. The Stub is called from the software component to be tested.

Tests top layer of controlling subsystem first. Then combine modules that are called by the tested modules and test resulted collection of modules.

Do this until all the modules are combined and tested.

The Bug Tracking System role is discussed below:

- Testers and developers can know the status of the bug at every stage.

- Changes to the Status will be available to all team members.

- Developers and Testers can easily interact with bugs.

- Repetition of bugs will be avoided.

- Easy to distribute the bug among the developer.

- It will act as a centralized one for defects.

Time Estimation method for Testing Process:

Step 1 : count number of use cases (NUC) of system 

Step 2 : Set Avg. Time Test Cases(ATTC) as per test plan 

Step 3 : Estimate total number of test cases (NTC) 

Total number of test cases = Number of Use Cases X Avg. Test Cases per a use case 

Step 4 : Set Avg. Execution Time (AET) per a test case 

Step 5 : Calculate Total Execution Time (TET) 

TET = Total number of test cases * AET 

Step 6 : Calculate Test Case Creation Time (TCCT)

usually we will take 1.5 times of TET as TCCT

TCCT = 1.5 * TET

Step 7 : Time for Re-Test Case Execution (RTCE) this is for retesting

usually we take 0.5 times of TET

RTCE = 0.5 * TET

Step 8 : Set Report generation Time (RGT

usually we take 0.2 times of TET

RGT = 0.2 * TET

Step 9 : Set Test Environment Setup Time (TEST)

it also depends on test plan

Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer.

Use Case: A use case is a description of the process which is performed by the end user for a particular task. Use case contains a sequence of step which is performed by the end user to complete a specific task or a step by step process that describe how the application and end user interact with each other. Use case is written by the user point of view.

Use case Testing: the use case testing uses this use case to evaluate the application. So that, the tester can examines all the functionalities of the application. Use case testing cover whole application, tester performs this testing in step by step process to complete one task

The benefits of Automation Testing are below:

- Test engineer productivity.

- Coverage of regression testing.

- Reusability of test cases.

- Consistency in testing.

- Test interval reduction

- Reduced software maintenance cost

- Increased test effectiveness

Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this tester enter the data in any format and check the software is not crashing. In this testing we use Smart monkey and Dumb monkey.

- Smart monkeys are used for load and stress testing, they will help in finding the bugs. They are very expensive to develop.

- Dumb monkey, they are important for basic testing. They help in finding those bugs which are having high severity. Dumb monkey are less expensive as compare to Smart monkeys.

Example: In phone number filed Symbols are entered.

EX:

- High Priority and Low Severity:

Company logo is not properly displayed on their website.

- High Priority and High Severity:

Suppose you are doing online shopping and filled payment information, but after submitting the form, you get a message like "Order has been cancelled."

- Low Priority and High Severity:

If we have a typical scenario in which the application get crashed, but that scenario exists rarely.

- Low Priority and Low Severity:

There is a mistake like "You have registered success" instead of successfully, success is written.

Quality Assurance (QA): QA refers to the planned and systematic way of monitoring the quality of process which is followed to produce a quality product. QA tracks the outcomes and adjusts the process to meet the expectation.

Quality Control (QC): Concern with the quality of the product. QC finds the defects and suggests improvements. The process set by QA is implemented by QC. The QC is the responsibility of the tester.

Software Testing: is the process of ensuring that product which is developed by the developer meets the user requirement. The motive to perform testing is to find the bugs and make sure that they get fixed.