Fresher Interview Questions with Answers

Fresher Interview Questions with Answers

This blog explains about Fresher Interview Questions with Answers and is given below : 

           1.  Service Based Company

     Product Based Company  

i)They fulfill software requirements for a client They create their own product
ii) Requirements are gathered  using client Requirements are gathered based on  customer feedback, Market Survey. R & D department
iii)Example for service based companies

CTS, TCS, Wipro, Infosys

Example for product  based companies

Oracle, Microsoft              

2. Manual Testing

Automation Testing

i)Testing the software manually by giving inputs manually and verifying the functionality of the application is Manual Testing Writing a program and having the application to be tested for it functionality and performance with out any manual intervention is Automation Testing
ii)It is also called as Black box Testing Automated testing can be white box or black box  Testing
iii)Programming knowledge is not preferred Programming knowledge is  preferred

3.Test Cases

Test Script

i)It is a document consists of step by step instruction or procedure  to check the functionality  & stability of the application It is a set of instruction  wrriten using scripting or programming language to test the functionality of the application
ii)Normally test cases are used in Manual Testing Test script’s are used in Automation Testing

4.Programming language

Scripting Language

i)Programming language  needs compilation Scripting languages do not require the compilation
ii)Examples for  programming languages are Java, C, C++ Examples for  scripting  languages are JavaScript, perl
iii)Applications of Scripting Languages :

 

1. To automate certain tasks in a program

 

2. Extracting information from a data set

 

3. Less code intensive as compared to traditional programming languages

Applications of Programming Languages :

 

1. They typically run inside a parent program like scripts

 

2. More compatible while integrating code with mathematical models

 

3. Languages like JAVA can be compiled and then used on any platform

5.SDLC

STLC

i)It is systematic approach to develop a software It is a systematic approach to test a software
ii)Customer , Developer, Testing Enginner , Project Architect, Client  etc takes part in this cycle Testing Engineer  responsible for the whole cycle

6.Regression Testing

Retesting

i)Because of adding a new feature, old feature might have impacted , testing the old feature is called as Regression testing Testing only the defected areas are called Retesting
ii)In regression testing passed test cases are executed . In retesting  failed test cases are executed

7.Smoke Testing

Sanity Testing

i)Testing the critical funtionality of the application is Smoke Testing It is done whenever a quick round of software testing can prove that the software application is functioning according to business / functional requirements.
ii)Smoke Testing  is formal way for testing the software Sanity Testing is informal way for testing the software
iii)For  Smoke testing, Test cases and Test scripts are  generated for Manual or Automation execution For Sanity testing test cases and test scripts will not be used.

8.Testing

Debugging

i)Fundamentally, testing is a process to check if the system is working same as it was supposed to do, and not working as it was not supposed to do. It is done by the tester to identify the defects in the system (actual result of test case execution is not matching with expected result). Debugging is the activity performed by developers to fix the bug found in the system. This is manual step by step unstructured and unreliable process to find and removes a specific bug from the system.
ii)It is done by the tester to identify the defects in the system (actual result of test case execution is not matching with expected result). Based on the defects reported, the developer starts analyzing the root cause of the defect to make system defect free. The developers need to fix the code to make actual result same as expected result.
iii)Testing is the process which can be planned, designed and executed Debugging is the process which cannot be so forced.
iv)Testing is a process of finding bugs or errors in a software product that is done manually by tester. Debugging is a process of fixing the bugs found in testing phase. Programmer or developer is responsible for debugging and it can’t be automated.

9.Severity

Priority

i)Severity of a defect is related to how severe a bug is. Usually the severity is defined in terms of financial loss, damage to environment, company’s reputation and loss of life. Priority of a defect is related to how quickly a bug should be fixed and deployed to live 
ii)Severity  is associated with standards Priority is associated with scheduling
iii)Severity is categorized  into Critical, Major, Minor, Low Defect Priority is categorized into Immediate, High, Medium, Low

10.Alpha Testing

Beta Testing

i)This is a form of internal acceptance testing performed mainly by the in-house software QA and testing teams.
ii)Alpha testing is the last testing done by the test teams at the development site after the acceptance testing and before releasing the software for beta test.  

This is the final testing phase where the companies release the software to few external user groups outside the company test teams or employees.

iii)To evaluate the quality of the product  To evaluate customer satisfaction
iv)Focus on finding bugs Focus on collecting suggestions / feedback and evaluate them effectively
v)Does the product work? Do customers like the product?

11. Static Testing

Dynamic Testing

i)Static Testing , it is also called as Static Testing Dynamic Testing is called as Validation
ii)Static Testing is type of testing in which the code is not executed. It can be done manually or by a set of tools. Dynamic testing is done when the code is in operation mode. 
iii)The Static test techniques include: Inspection, Walkthrough, Technical reviews, Informal reviews The Dynamic  test techniques include: Unit Testing, Integration Testing, System Testing, Acceptance Testing

12.Functional Testing

Non – Functional Testing

i)Functional Testing is the type of testing done against the business requirements of application. It is a black box type of testing. Non Functional Testing how much time does the software will take to complete a task? or how fast the response is.
ii)Functional Tetsting can be achieved using set of tools The non functional tests can be effective by using testing tools.
iii)Eg tools are: Selenium, UFT etc Eg tools are: J meter, Load Runner etc

13.Quality Assurance

Quality Control

i)The function of software quality that assures that the standards, processes, and procedures are appropriate for the project and are correctly implemented.  The function of software quality that checks that the project follows its standards, processes, and procedures, and that the project produces the required internal and external (deliverable) products.
ii)The goal of Quality Assurance is to prevent introducing defects in the software application which help to improve the development and testing processes. The goal of Quality Control is to identify the defects in the software application after it is developed.
iii)Quality Assurance is process oriented Quality Control is product oriented

14.Test Plan

Test Strategy

i)The test plan is a document that lists all the activities in a QA project, Test strategy is going to have details like – Individual modules are to be tested by test team members. 
ii)Test plan is derived from SRS (Software Requirement Specification) which is prepared by test lead or manager. Test strategy is developed by project manager or business analyst.
iii)Test plan contains: Test plan ID, Test Environment, Features to be tested/Not tested, Entry/Exit criteria, Status, Types of testing, Brief Intro Test Strategy contains Scope and objective, Business Issues, Testing approach, Test deliverables, Defect tracking approach, Training, Automation, Risks
iv)Test plan is often not updated but if there is some new feature or change is introduced then it has to be updated accordingly. Test strategy should not be modified very often because it sets some standards for test plan and if standards are modified frequently then it becomes difficult to stick to a particular plan and changing plan frequently will affect the quality of the testing.

15.Black Box Testing

White Box Testing

i)It is the testing done by the professional testing enginner by looking into the application, they are not exposed to the logic of the code or the flow of the code It is the testing done by the development team often the completion of coding, This is done by looking into the internal Behaviuor of Logic of the code and flow of the code
ii)It is done by Tester , Developer, Customer Done by developer
iii)It is also called as functional testing It is  also called as Unit testing, Transparent testing
iv)Highly time consuming & exhaustive Least time consuming and not exhaustive

16.Load Testing

Stress Testing

i)Testing the stability  & response time of the application by applying a desired load less than or equals to the desired number is Load testing Applying load greater than the desird load and checking the response time of an application is called as Stress Testing
ii)Load testing is usually started as low numbers and gradually increased over a given period of time until it reaches the desired load on the system and then it ramps down. Stress testing starts of the same as load testing, e.g. gradually increasing load on the servers, the process is repeated till the time the load is reached to the unexpected limits.

 

17.Stubs

Drivers

i)It is a dummy piece of module which is created as a substitue for child module It is a dummy piece of module which is created as a substitue for parent module
ii)Stubs used in Top-Down Approach Drivers used in Bottom-Up Approach
iii)It is used to check the communication from parent to child It is used to check the communication from child to parent

                                                                             –  AUTHOR 

                                                                                  KOGUL

REFERENCES :

https://stackoverflow.com/questions/10535081/what-is-the-main-diffrence-between-whitebox-testing-and-automation-testing

https://www.geeksforgeeks.org/whats-the-difference-between-scripting-and-programming-languages/

http://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.html

https://www.softwaretestingclass.com/difference-between-testing-and-debugging/

https://www.testingexcellence.com/severity-and-priority-difference/

https://www.softwaretestinghelp.com/how-to-set-defect-priority-and-severity-with-defect-triage-process/

https://www.softwaretestinghelp.com/static-testing-and-dynamic-testing-difference/

https://www.softwaretestingclass.com/difference-between-static-testing-and-dynamic-testing/

https://www.softwaretestingclass.com/functional-testing-vs-non-functional-testing/

https://www.softwaretestingclass.com/difference-between-quality-assurance-qa-and-quality-control-qc/

http://toolsqa.com/software-testing/differences-between-performance-load-and-stress-testing/