Search here

Pages

What Is System Testing



What Is System Testing

Testing the behavior of the whole software/system as defined in software requirements specification (SRS) is known as system testing, its main focus is to verify that the customer requirements are fulfilled.

System testing is done after integration testing is complete. 

In system testing, there are two type of testing

System Testing
Click on the image for zoom view

Functionality testing is to test whether application functioning as per requirement or not.

Non-functionality testing are several types :
  • Load,
  • Stress,
  • Performance,
  • Reliability,
  • Security,
  • Usability
  • Configuration,
  • Compatibility (forward & Backward),
  • Scalability, Etc...

Click on the links to read more about Functionality testing and Non-functionality testing

Different Types Of White Box Testing



Different Types Of White Box Testing

Path Testing :

Taking up each and every individual path through which the flow of code taken place.

Loop Testing :

A Piece of code executing continuously until the condition becomes false and testing whether it is proper or not.

Ex: For (Loop=1; Loop<=10; Loop++)
      {
        ------
        ------
       }

Bug Life Cycle Or Defect Life Cycle In Software Testing



Bug Life Cycle Or Defect Life Cycle In Software Testing

Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing.
Bug-life-cycle
Click on the image for zoom view

Automation Testing Interview Questions



Automation Testing Interview Questions

  1. What are principles of good testing scripts for automation?
  2. What are some of the common misconceptions during implementation of an automated testing tools for the first time?
  3. What are the limitations of automating software testing?
  4. What are the main attributes of test automation?
  5. Can test automation improve test effectiveness?

Integration Testing And Types Of Integration Testing



Define Integration Testing And Types Of Integration Testing

Integration Testing:

Combining the modules and testing the flow of data between them. Integration Testing is divided into 2 types.

  • Incremental Integration Testing:

Adding the modules incrementally and checking the data flow between them. Modules are added in a sequential fashion.

This can be done in two ways 
    • Top-Down Approach
    • Bottom-Up approach.

Define Agile Model and its Advantages



Define Agile Model and its Advantages

Agile Model or Agile Methodology :

Agile development methodology attempts to provide many opportunities to assess the direction of a project throughout the development life cycle. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames that typically last from one to four weeks. Each iteration involves a cross functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release at the end of each iteration. Multiple iterations might be required to release a product or new features.
agile-model

Software Testing Life Cycle (STLC)



Software Testing Life Cycle (STLC)

Software Testing Life Cycle (STLC) defines the steps/stages/phases in testing of software. 

The different stages in Software Testing Life Cycle:


  1. Requirement Analysis
  2. Test Planning
  3. Test Case Design / Development
  4. Environment setup
  5. Test Execution / Reporting / Defect Tracking
  6. Test Cycle Closure / Retrospective study

Software_Testing_Life_Cycle

Difference Between Severity And Priority



Difference Between Severity And Priority

Severity
Priority
Severity: It is with respect to the Impact on the functionality. It is with respect to the impact on the business.
Example for High Severity:

The Quarterly statement event is not triggering from the website and we are just at the beginning of the new quarter after a new release. In this case the Severity is High but priority could be low because we have time till the quarter end to fix the bug.
Example for High Priority:

The client logo is not appearing on the web site but the site is working fine. in this case the severity is low but the priority is high because from company's reputation it is most important to resolve. After all the reputation wins more clients and projects and hence increases revenue.

What If There Isn't Enough Time For Thorough Testing?



What If There Isn't Enough Time For Thorough Testing?

Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions:

  • Which functionality is most important to the project's intended purpose? 
  • Which functionality is most visible to the user? 
  • Which functionality has the largest safety impact? 
  • Which functionality has the largest financial impact on users? 

Difference Between Verification And Validation



Difference Between Verification And Validation

Verification
Validation
Are we building the product right? Are we building the right product?
Verification is to check whether software conforms to the specifications and is done by development team at various development phases.During development phase the SRS document ,Design Document and the code are reviewed to ensure that product is being developed using the process oriented approach.It is an in-house activity of the development organization. It is an Quality assurance activity which prevents the defects of the product. Validation is to check whether the software meets the customer's expectation.This is done by testing the software for its functionality and other requirements as mentioned in Requirements Specification Documents.Validation is carried out with customer involvement.It is Quality control acitvity which detects the defect during testing of the product

Difference Between Test Scenario And Test Case



Difference Between Test Scenario And Test Case

Test Scenario
Test Case
Test Scenario is ‘What to be tested’ Test Case is ‘How to be tested’
Test scenario is nothing but test procedure. Test case consist of set of input values, execution precondition, expected Results and executed post-condition developed to cover certain test Condition.
The scenarios are derived from use cases. Test cases are derived (or written) from test scenario.
Test Scenario represents a series of actions that are associated together. Test Case represents a single (low level) action by the user.
Scenario is thread of operations Test cases are set of input and output given to the System.

For example:
  • Checking the functionality of Login button is Test scenario
  • Test Cases for this Test Scenario are:
    • Click the button without entering user name and password.
    • Click the button only entering User name.
    • Click the button while entering wrong user name and wrong password and etc...

Web Testing Interview Questions Answers



Web Testing Interview Questions Answers

web-testing-interview-questions

What is Web application?

  • It is Software application that is accessed over a network such as the Internet or an intranet through a web browser. Web application provides services (Free and Paid) apart from information. Ex: Online Banking System it provides Bank information, Branches & ATM Information, Loans information etc…And It provides balance enquiry, Fund transfer, Bill payments like services.

What is Web browser?

  • Web browser is a software application used to locate, retrieve and also display content on the World Wide Web, including Web pages, images, videos and other files. Examples: Google Chrome, Mozilla Firefox, Internet Explorer, Opera, Safari.

What is website?

  • Basically website is an information provider; it provides information globally using internet protocols.

Top 100 Software Testing Interview Questions



Top 100 Software Testing Interview Questions

  1. What are the common problems with software automation?
  2. What are the key challenges of software testing?
  3. What is the role of QA in a project development?
  4. Can you explain V model in manual testing?
  5. Can u explain the structure of bug life cycle?
  6. What is “bug leakage?” and what is “bug release?”
  7. Can you explain water fall model in manual testing?
  8. Can you explain me the levels in V model manual?

Compare Desktop testing, Client-Server testing and Web testing



We have three testing types
  • Desktop application testing,
  • Client server application testing and
  • Web application testing.
Each one differs in the environment in which they are tested and you will lose control over the environment in which application you are testing, while you move from desktop to web applications.

DESKTOP APPLICATION:

It runs on personal computers and work stations, so when you test the desktop application you are focusing on a specific environment. You will test complete application broadly in categories like GUI, functionality, Load, and back-end i.e DB.

CLIENT / SERVER TESTING:

In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, back-end.

Difference between Web testing and Client-Server testing



Difference between Web testing and Client-Server testing :

CLIENT / SERVER TESTING
WEB TESTING
This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having frontend and backend.

The application launched on frontend will be having forms and reports which will be monitoring and manipulating data

This is done for 3 tier applications (developed for Internet / intranet / xtranet)

Here we will be having Browser, web server and DB server.

The applications accessable in browser would be developed in HTML, DHTML, XML, JavaScript etc.,
(we can monitor thru these applications)
Applications developed in VB,VC++,Core Java,C,C++,D2K,PowerBuilder etc.,

Applications for the webserver would be developed in Adv Java, ASP, JSP, VBScript, JavaScript, Perl, ColdFusion, PHP etc.,
(all the manipulations are done on the web server with the help of these programs developed)

The backend for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase

The DBserver would be having oracle, sql server, sybase, mysql etc.,
(all data is stored in the database available on the DB server)
The tests performed on these type of applications would be
- user interface testing
- manual support testing
- Functionality testing
- compatability testing & configuration testing
- intersystems testing

The tests performed on these type of applications would be
- user interface testing
- Functionality testing
- security testing
- browser compatability testing
- load / stress testing
- interoperability testing/intersystems testing
- storage and data volume testing

Software testing Interview Questions – Based on Testing Levels



Software testing Interview Questions – Based on Testing Levels

  •  What is Acceptance Testing?
  • What is Alfa Testing?
  • What is Beta Testing?
  • What is Big-bang or System Approach?
  • What is Bottom-up Integration?
  • What is Certification Testing?