Difference between Agile and SAFe® Agile

The Scrum Guide states that, the “essence of Scrum is a small team of people.” Which

would be fine if all our projects were small and didn’t need to scale beyond that small

team. We can handle scaling between functions or teams by using native Scrum of

Scrums. But once we scale much beyond that then it is necessary to begin considering a

scalable framework.

So, the main difference between Agile and Scaled Agile is that Agile was designed for

small teams with specific roles, whereas Scaled Agile is designed to scale all the way up

to the enterprise.

Comparison of Scrum and Scaled Agile

Framework

Agile SAFe®

Has defined roles – (Kanban does not) Has several defined roles

Small core team size Small core team size

Planning is done prior to the first sprint and at the Planning is done at a timebox called a Program
beginning of each sprint Increment.

Scales between teams Scales to the enterprise

 Agile SAFe®

Framework has no defined levels Framework has four defined levels

Has core values – Built-in quality, transparency

Has core values – Agile Manifesto and twelve principles
program execution and alignment

Is focused on customer and business value Is focused on customer and business value

Does not describe value stream Value stream is a key element

Strives to achieve continuous delivery Strives to achieve continuous delivery

https://www.softwaretestinghelp.com/software-testing-interview-questions/

https://stackify.com/what-is-sdlc/

SDLC:

 Requirement analysis
 Planning
 Software design such as architectural design
  Software development
 Testing
 Deployment

Functional testing types

https://www.applause.com/blog/functional-testing-types-
examples

Let’s explore these types of functional tests with examples:

 Unit testing
  Component testing
 Smoke testing
 Sanity testing
 Regression testing
 Integration testing
 API testing
 UI testing
 System testing
 White-box testing
 Black-box testing
 Acceptance testing
 Alpha testing
 Beta testing
 Production testing

Ad hoc Testing
Ad hoc Testing is an informal or unstructured software testing type that aims to
break the testing process in order to find possible defects or errors at an early
possible stage. Ad hoc testing is done randomly and it is usually an unplanned
activity which does not follow any documentation and test design techniques to
create test cases.

How To Select Correct Test Cases For

Automation Testing (And Ultimately
Achieve A Positive Automation ROI)
One of the key steps to commence Automation Testing is – selecting the
appropriate test cases and determining the ROI (Return On Investment).

 The task is going to be repeated.

 It’s going to save time.
 The requirements, the test, or the task are low risk, stable,
and unlikely to change often.
  The test is subject to human error.
 The test is time consuming.
 The test has significant downtime between steps.
 The test is repetitive.

 Test case executed with different sets of data.

 Test case executed with different browsers.
 Test case executed with different environments.
 Test case executed with complex business logic
 Test case executed with a different set of users
 Test case involves a large amount of data
 Test case has any dependency
 Test case requires Special data

The STLC has several interconnected phases and is generally very similar to
the SDLC system. These phases are sequential and are called:

1. Requirement Analysis;
2. Test Planning;
3. Test Case Development;
4. Test Environment Setup;
5. Test Execution;
6. Test Cycle Closure.
Q #1) What is Dynamic Testing?
Answer: Dynamic testing is done by executing the code or program with various input
values and later on the output is verified.
Q #2) What is GUI Testing?
Answer: GUI or Graphical User Interface testing is the process of testing the software's
user interface against the provided requirements/mockups/HTML designs etc.,
Q #3) What is Formal Testing?
Answer: Software verification, carried out by following a test plan, testing procedures and
proper documentation with approval from the customer is termed as Formal Testing.
Q #4) What is Risk-Based Testing?
Answer: Identifying the critical functionality in the system and then deciding the orders in
which these functionalities are to be tested and perform testing is termed as Risk-based
Testing.
Q #5) What is Early Testing?
Answer: Perform testing as soon as possible in the development lifecycle to find defects at
the early stages of STLC. Early testing is helpful to reduce the cost of fixing defects at the
later stages of STLC.
Q #6) What is Exhaustive Testing?
Answer: Testing functionality with all valid, invalid inputs and pre-conditions is called
Exhaustive testing.
Q #7) What is Defect Clustering?
Answer: Any small module or functionality may contain a number of defects and to
concentrate more on testing these functionalities is known as Defect Clustering.
Q #8) What is Pesticide Paradox?
Answer: If already prepared test cases do not find defects, add/revise test cases to find
more defects, this is known as Pesticide Paradox.
Q #9) What is Static Testing?
Answer: Manual verification of the code without executing the program is called Static
Testing. In this process, the issues are identified in the code by verifying code, requirement
and design documents.
Q #10) What is Positive Testing?
Answer: It is the form of testing which is conducted on the application to determine if the
system works properly or not. Basically, it is known as the “test to pass” approach.
Q #11) What is Negative Testing?
Answer: Testing software with a negative approach to check if the system is not “showing
error when not supposed to” and “not showing error when supposed to” is termed as
Negative Testing.
Q #12) What is an End-to-End Testing?
Answer: Testing the overall functionality of the system including the data integration among
all the modules is called End-to-End Testing.
Q #13) What is Exploratory Testing?
Answer: Exploring the application, understanding its functionalities, adding (or) modifying
the existing test cases for better testing is called Exploratory testing.
Q #14) What is Monkey Testing?
Answer: Testing conducted on an application without any plan and carried out randomly
with the tests to find any system crash with the intention of finding tricky defects is called
Monkey Testing.
Q #15) What is Non-Functional Testing?
Answer: Validating various non-functional aspects of the system such as user interfaces,
user-friendliness, security, compatibility, Load, Stress, and Performance, etc., is called Non-
Functional testing.
Q #16) What is Usability Testing?
Answer: Checking how easily the end-users are able to understand and operate the
application is called Usability Testing.
Q #17) What is Security Testing?
Answer: Validating whether all security conditions are properly implemented in the software
(or) not is called Security testing.
Q #18) What is Performance Testing?
Answer: The process of measuring various efficiency characteristics of a system such as
response time, load stress transactions per minute, transaction mix, etc., is termed
Performance Testing.
Q #19) What is Load Testing?
Answer: Analyzing both the functional and performance behavior of an application under
various conditions is called Load Testing.
Q #20) What is Stress Testing?
Answer: Checking the application behavior under stress conditions
(or)
Reducing the system resources and keeping the load as constant and checking how the
application is behaving is called Stress Testing.
Q #21) What is Process?
Answer: A process is a set of practices performed to achieve a given purpose; it may
include tools, methods, materials or people.
Q #22) What is Software Configuration Management?
Answer: The process of identifying, organizing and controlling changes to Software
development and maintenance.
(or)
It is a methodology to control and manage a software development project.
Q #23) What is a Testing Process / LifeCycle?
Answer: It includes the below factors:
 Writing a Test Plan
 Test Scenarios
 Test Cases
 Executing the Test Cases
 Test Results
 Defect Reporting
 Defect Tracking
 Defect Closing
 Test Release
Q #24) What is the full form of CMMI?
Answer: Capability Maturity Model Integration
Q #25) What is a Code Walk Through?
Answer: An informal analysis of the program source code to find the defects and verify the
coding techniques is termed as a Code Walk Through.
Q #26) What is Unit Level Testing?
Answer: Testing of single programs, modules or unit of code is termed as Unit Level
Testing.
Q #27) What is Integration Level Testing?
Answer: Testing of related programs, modules (or) unit of code.
(or)
Partitions of the system which are ready for testing with other partitions of the system are
termed as Integration level testing.
Q #28) What is System Level Testing?
Answer: Testing of the entire computer system across all the modules is termed as
System-level testing. This kind of testing can include Functional as well as Structural
Testing.
Q #29) What is Alpha Testing?
Answer: Testing of a whole computer system before rolling out to the UAT is termed as
Alpha testing.
Q #30) What is User Acceptance Testing (UAT)?
Answer: UAT is the form of testing of a computer system by the client to verify if it adhered
to the provided requirements or not.
Q #31) What is a Test Plan?
Answer: It is a document describing the scope, approach, resources, and schedule of
testing activities. It identifies test items, features to be tested, testing tasks, who will do
each task, and any risks requiring contingency planning.
Q #32) What is a Test Scenario?
Answer: Identifying all the possible areas to be tested (or) what is to be tested is termed as
Test Scenario.
Q #33) What is ECP (Equivalence Class Partition)?
Answer: It is a method for deriving test cases.
Click here to know more.
Q #34) What is a Defect?
Answer: Any flaw or imperfection in a software work product is termed as a Defect.
(or)
When the expected result does not match with the application actual result, it is termed as a
Defect.
Q #35) What is Severity?
Answer: It defines the importance of the defect from the functional point of view i.e. how
critical is a defect with respect to the application.
Q #36) What is Priority?
Answer: It indicates the importance or urgency of fixing a defect
Q #37) What is Re-Testing?
Answer: Re-testing the application means verifying whether the defects have been fixed or
not.
Q #38) What is Regression Testing?
Answer: Verifying an existing functional and non-functional area after making changes to
the part of a software or addition of new features is termed as Regression Testing.
Q #39) What is Recovery Testing?
Answer: Checking whether the system is able to handle some unexpected or unpredictable
situations is called Recovery Testing.
Q #40) What is Globalization Testing?
Answer: It is the process of verifying whether the software can be run independently of its
geographical and cultural environment. Verifying if the application has the feature to set and
change language, date, format, and currency or if it is designed for global users.
Q #41) What is Localization Testing?
Answer: Verifying globalized application for a particular locality of users, under cultural and
geographical conditions is termed as Localization Testing.
Q #42) What is Installation Testing?
Answer: Checking whether we are able to install a software successfully (or) not, as per the
guidelines given in the installation document is called Installation Testing.
Q #43) What is Un-Installation Testing?
Answer: Checking whether we are able to uninstall the software from the system
successfully (or) not is called Un-Installation Testing
Q #44) What is Compatibility Testing?
Answer: Checking whether the application is compatible with different software and
hardware environment or not is called Compatibility Testing.
Q #45) What is a Test Strategy?
Answer: It is a part of a test plan describing how testing is carried out for the project and
what testing types need to be performed on the application.
Q #46) What is a Test Case?
Answer: A Test case is a set of pre-conditional steps to be followed with input data and
expected behavior to validate the functionality of a system.
Q #47) What is Business Validation Test Case?
Answer: A test case that is prepared to check the business condition or a business
requirement is called the Business Validation test case.
Q #48) What is a Good Test Case?
Answer: A Test case that has a high priority of catching defects is called a Good Test
Case.
Q #49) What is Use Case Testing?
Answer: Validating a software to confirm whether it is developed as per the use cases or
not is called Use Case testing.
Q #50) What is a Defect Age?
Answer: The time gap between the date of detection & the date of closure of a defect is
termed as Defect Age.
Q #51) What is the Showstopper Defect?
Answer: A defect that does not permit testing to continue further is called Showstopper
Defect.
Q #52) What is a Test Closure?
Answer: It is the last phase of the STLC, where the management prepares various test
summary reports that explain the complete statistics of the project based on the testing
carried out.
Q #53) What is Bucket Testing?
Answer: Bucket testing is also known as A/B testing. It is mostly used to study the impact
of various product designs on website metrics. Two simultaneous versions run on a single
or a set of web pages to measure the difference in click rates, interface, and traffic.
Q #54) What is meant by Entry Criteria and Exit Criteria in Software Testing?
Answer: Entry Criteria is the process that must be present when a system begins, like,
 SRS – Software
 FRS
 Use Case
 Test Case
 Test Plan
Exit criteria ensure whether the testing is completed and the application is ready for
release, like,
 Test Summary Report
 Metrics
 Defect Analysis Report
Q #55) What is Concurrency Testing?
Answer: This is a multiple user testing to access the application at the same time to verify
the effect on code, module or DB and it is mainly used to identify the locking and
deadlocking situations in the code.
Q #56) What is Web Application Testing?
Answer: Web application testing is done on a website to check – load, performance,
security, functionality, interface, compatibility and other usability-related issues.
Q #57) What is Unit Testing?
Answer: Unit testing is done to check whether the individual modules of the source code
are working properly or not.
Q #58) What is Interface Testing?
Answer: Interface testing is done to check whether the individual modules are
communicating properly as per the specifications or not. Interface testing is mostly used to
test the user interface of GUI applications.
Q #59) What is Gamma Testing?
Answer: Gamma testing is done when the software is ready for release with the specified
requirements, this testing is done directly by skipping all the in-house testing activities.
Q #60) What is the Test Harness?
Answer: Test Harness is configuring a set of tools and test data to test an application under
various conditions, which involves monitoring the output with the expected output for
correctness.
The benefits of Testing Harness are: Productivity increase due to process automation
and increase in the product quality
Q #61) What is Scalability Testing?
Answer: It is used to check whether the functionality and performance of a system are
capable to meet the volume and size changes as per the requirements.
Scalability testing is done using the load test by changing various software, hardware
configurations, and testing environment.
Q #62) What is Fuzz Testing?
Answer: Fuzz testing is a black-box testing technique that uses random bad data to attack
a program to check if anything breaks in the application.
Q #63) What is the difference between QA, QC, and Testing?
Answer:
 QA: It is process-oriented and its aim is to prevent the defects in an application.
 QC: QC is product-oriented and it is a set of activities used to evaluate a developed
work product.
 Testing: Executing and verifying an application with the intention of finding defects.
Q #64) What is Data-Driven Testing?
Answer: It is an Automation testing process in which an application is tested with multiple
sets of data with different preconditions as an input to the script.

Q #1) What do you understand by web application?

Answer: Web application is a means to communicate and exchange information with
customers. Unlike any desktop applications which are executed by an operating system, a
web application runs on a web server and is accessed by a web browser that acts as a
client.
The best example of a web application is ‘Gmail’. In Gmail, the interaction is done by an
individual user and is completely independent of the others. You can send and receive
information through emails and also through attachments.
You can maintain documents in a drive, maintain spreadsheets in Google docs and includes
much more such features which make a user realize that they have an environment which is
customized to their specific identity.

Q #2) Define a Web server.

Answer: Web server follows the client/server model where the program uses HTTP
(Hypertext Transfer Protocol). In response to the request of an HTTP client, the webserver
handles client and server-side validation and delivers the web content in the form of web
pages to the users.
The browsers, such as Safari, Chrome, Internet Explorer, Firefox, etc., read the files stored
on the web servers and bring the information to us in the form of images and texts with the
means of the internet. Any computer which hosts websites must have web servers.

Some of the leading web servers are:

 Apache
 Microsoft’s Internet Information Server (IIS)
 Java webserver
 Google web server

Q #3) Enlist some important test scenarios for testing a website.

Answer: There are many parameters that should be considered while deciding the
important test scenarios for testing any website. Also, the type of website to be tested and
its requirement specification plays an important role here.
Enlisted below are few important test scenarios that are applicable for testing any
type of website:
 Test the GUI (Graphical User Interface) of the website for verifying the consistency
of the design elements and page layout.
 All page links and hyperlinks are checked for their redirection to the desired page.
 In case of presence of any forms or fields on the website, testing scenarios consist of
testing with valid data, invalid data, testing with existing records as well as testing
with empty records.
 Functionality testing as per the requirement specification is done.
 The performance of a website is tested under heavy loads to determine the web
server response time and database query time.
 Compatibility testing is done to test the behavior of an application on a different
browser and OS (operating system) combinations.
 Usability testing and Database testing is also performed as a part of test scenarios.
Q #4) What are the different configurations that have to be considered while testing a
website?
Answer: Different configuration includes different browsers as well as an operating system
on which a website is being tested. Browser plugins, text size, video resolution, color depth,
browser setting options are also considered when we talk about configurations.
Different combinations of browsers and operating systems are used to test the compatibility
of the website. Usually, the latest and the last latest versions are included. Well, these
versions are usually specified in the Requirement document.

Few important browsers include:

 Internet Explorer
  Firefox
 Chrome
 Safari
 Opera
Few important Operating systems include:
 Windows
 UNIX
 LINUX
 MAC
Q #5) Is Web Application testing different from Desktop Application testing? Explain
how.
Answer: Yes, enlisted below points in table explains the differences between web
application and desktop application.
Web Application Desktop Application

Definition Web applications are the one which can run on any Desktop applications are one which
client machine having the internet connection without separately installed and executed on
any installation of the execution file. personal computer.

Performance User actions, feedback, statistics can be easily User actions cannot be monitored as
monitored as well as data updating in one place is changes in data can be only reflected
reflected everywhere in web application. machine.

Connectivity Desktop application can be only acce

Web application can be accessed on any PC having specific PC where application is inst
internet connection using web browser where
performance of the application depends on internet
speed.

Security Desktop application is less prone to

Risks Web application is more prone to security threats as threats where user can keep a check
applications can be accessed by anyone on the internet. security issues at the system level.

User data Data is stored, saved and accessed fr

User data is saved and accessed remotely in case of web same machine on which application
applications. installed.
Q #6) What is the Intranet Application?
Answer: Intranet application is a kind of private application that is deployed and run on a
local LAN server and can only be accessed by the people within the organization. It uses a
local network to share information.
For Example, Organization usually has an application that stores information about your
attendance, holidays, upcoming celebrations within the organization or some important
event or information that needs to be circulated within the organization.
Q #7) Explain the difference between Authorization and Authentication in Web
testing.
Answer: The difference between Authorization and Authentication is explained in the
below table:
Authorization
Authentication

1 Authentication is the process with which the Authorization is the process with which system identi
system identifies who the user is? what user is authorized to do?

2 Authentication determines the identity of the user. Authorization decides the privileges given to the user
whether the user can access or manipulate features of
program.

3 There are different types of authentications, like There are two types of authorizations, like read only a
password based, device based, etc. write both.

4 For example: Within an organization, each and For example: Only account manager or person in acco
every employee can login into an intranet department can access account section.
application.
Q #8) What are the types of Web testing security problems?
Answer: Few web security problems include:
 Denial of Service (DOS) attack
 Buffer overflow
 Directly passing internal URL through browser address
 Viewing other stats
Q #9) Define HTTP.
Answer: HTTP stands for Hypertext Transfer Protocol. HTTP is the data transfer protocol
that defines how messages are formatted and transferred over the World Wide Web. HTTP
also determines the response of the actions performed by web servers and browsers.
For Example, when an URL is entered on the web browser, the HTTP command is sent to
the webserver which in turn fetches the requested web browser.
Q #10) Define HTTPS.
Answer: HTTPS stands for Hypertext Transfer Protocol Secure. This is basically HTTP
over SSL (Secure Socket Layer) for security purposes. There are always chances of
eavesdrop on data being transferred between a user and the web server when the website
uses HTTP protocol.
Therefore, websites use a secure way i.e. SSL encryption of data sent back and forth using
HTTPS protocol. Almost all the websites that require user log-in use HTTPS protocol. For
Example, banking websites, e-commerce websites, etc.
Q #11) What are the common problems faced in Web testing?
Answer: Some of the common problems faced in web testing are enlisted below:
 Server Problem, which includes server down and server under maintenance
problems.
 Database connection problem.
 Hardware and browser compatibility problems.
 Security-related problems.
 Performance and load-related problems.
  GUI (Graphical User Interface) related problems.
Q #12) What is Cookie testing?
Answer: Cookie is said to be a personalized user’s identity or information that is required to
communicate between different web pages as well as track user’s navigation through the
website pages. Whenever we access any website on any web browser, their respective
cookie is written on the hard disk.
Cookies are used to track user sessions, displays ads, remember user’s choice while
accessing any website, remember and retrieve the user’s shopping cart, track the unique
number of visitors, etc.

Suppose an e-commerce site is accessible in many countries like the US, Canada,
Australia, and their testing is done in India. In that case, while testing the e-commerce site
for different countries in India, at first respective countries cookies is set so that actual data
like time zone, etc., are accessed of that particular country.

Q #13) Define Client-side validation.

Answer: Client-side validation is the one which is basically done at the browser level where
the user’s input is validated at the browser itself with no involvement of the server.
Let's understand it with the help of an Example.
Suppose a user is entering an incorrect email format while filling a form. The browser will
instantly prompt an error message to correct it before moving on to the next field. Thus
every field is corrected before submitting the form.

The client-side validation is usually done by script language such as JavaScript, VBScript,
HTML 5 attributes.

The two types of Client-side validation are:

 Field-level validation
 Form level validation
Q #14) What do you understand by Server-side validation?
Answer: Server-side validation occurs where the validation and processing of user
requests require the response from the server. To understand it more clearly, the user’s
input is being sent to the server and validation is done using server-side scripting languages
such as PHP, Asp.NET, etc.
After the validation process, feedback is sent back to the client in the form of a dynamically
generated web page.

When compared to the Client-Side validation process, the Server-side validation process is
more secure because here application is protected against malicious attacks and users can
easily bypass client-side scripting language.

Q #15) Differentiate between Static and Dynamic website.

Answer: Difference between static and dynamic websites are as follows:
 Static Website Dynamic website

Static websites are the one which gives out Dynamic websites are the one where user interaction is
information only and there is no sort of interaction possible between the website and user along with impa
between the user and the website. information.

Static websites are cheapest to develop and host. Dynamic websites are more expensive to develop as w
their hosting cost is also more.

Static websites are easily loaded on client browser Dynamic websites usually take the time to load on clie
because of its fixed content and no database browser because contents to display are dynamically cr
connectivity. and retrieved using database queries.

Static websites can be created from HTML, CSS and Dynamic websites require server application language
does not require any server application language. ASP.NET, JSP, PHP to run the application on the serve
display the output on the webpage.

Change in the content of the page of any static Dynamic website provides facilities to change the page
website; require being uploaded on server many using server application.
times.
Q #16) What do you understand by Client-Server testing?
Answer: Client-server application is the one where the application itself gets loaded or
installed on a server whereas the application EXE file is loaded on all client machines. This
environment is usually used in Intranet networks.
Following tests are performed on a Client-server application:
 GUI testing on both client and server systems.
 Client-server interaction.
 The functionality of an application.
 Load and performance testing.
 Compatibility testing.
All the test cases and test scenarios used in client-server application testing is derived from
the tester’s experience and requirement specifications.

Q #17) Enlist HTTP response codes that are returned by the server.
Answer: HTTP response codes are enlisted below:
 2xx – This means ‘Success’
 3xx- This means ‘Redirection’
 4xx- This means ‘Application error’
 5xx- This means ‘Server error’
Q #18) What is the role of Usability testing in Web testing?
Answer: In web testing, Usability testing plays an important role. It is well known that
usability testing is the means to determine the ease with which an end-user can easily
access the application with or without having any programming language knowledge.
In terms of web testing, usability testing comprises of the following:
 To check whether the website is user-friendly?
 Is the end-user able to easily navigate within the application?
  Presence of any issues or ambiguity which can hinder the user experience.
 Check how quickly the user is able to complete the task within the application.
Q #19) What are the available environments on the Web?
Answer: The different types of the environment on the Web are:
 Intranet (Local Network)
 Internet (Wide Area Network)
 Extranet(Private network over the internet)
Q #20) What are the test case formats in the case of a Static website and Dynamic
website?
Answer: The following test case formats will be used in case of Static websites:
 Front-end test cases
 Navigation test cases
The following test case formats will be used in case of Dynamic websites:
 Front-end test cases
 Back-end test cases
 Navigation test cases
 Field validation test cases
 Security test cases, etc.
Q #21) Enlist some sub-classes of HTTP response objects?
Answer: Write, Flush, tell, etc are few HTTP response objects.
The sub-classes of HTTP response are:
 HttpResponseRedirect
 HttpResponsePermanentRedirect
 HttpResponseBadRequest
 HttpResponseNotfound
Q #22) Enlist some Web Testing Tools.
Answer: Few Web testing tools are enlisted below:
 eggplant functional
 Selenium
 SOA test
 JMeter
 iMacros, etc.
Q #23) Give some examples of web applications that are used in our day to day life.
Answer: Few examples include:
 Web portals like eBay, Amazon, Flipkart, etc.
 Banking applications like ICICI, Yes Bank, HDFC, Kotak Mahindra, etc.
 Email service providers like Gmail, Yahoo, Hotmail, etc.
 Social networks like Facebook, Twitter, LinkedIn, etc.
 Discussion and Information forums like www.Softwaretestinghelp.com
Q #24) What is a Proxy server?
Answer: The proxy server is a server that acts as an intermediary or is the one that lies
between the client and the main server.
The communication between the main server and client-server is done through a proxy
server as the client request of any connection, file, resources from the main server is sent
through a proxy server and again the response from the main server or local cached
memory to client-server is done through the proxy server.
Some of the most common proxy servers based on their purpose and functionality
are listed below:
 Transparent proxy
 Web proxy
 Anonymous proxy
 Distorting proxy
 High anonymity proxy
The proxy server is basically used for the following purposes:
 To improve the performance of web response.
 In case of the presence of a document in the cache memory, the response is directly
sent to the client.
 Proxy server filters web page content in the form of web proxies.
 A proxy server is also used to block offensive web content to be accessed by the
user especially in an organization, school, and college.
 Web proxies prevent the attack of computer viruses and malware.
Q #25) What is a Database server?
Answer: A Database server can be defined as a server that refers to the back-end system
of a database application that provides database services such as accessing and retrieving
data from the database.
The database server uses client/server architecture where the data can be accessed either
through the database server by a “front end” which runs and displays data on the user’s
machine or “back-end” which runs on the database server itself.

A database server is like a data warehouse and also holds on Database Management
System (DBMS).

Name:
Email:

Difference between Smoke Testing and Regression Testing :

S.No. Smoke Testing Regression Testing

Regression Testing is the Deep Level

01 Smoke Testing is the Surface Level Testing to verify the rationality of
. Testing to verify stability of system. system.

02 Smoke Test is always followed by Regression Test is always carried out

. Regression Test. throughout the testing phase.

03 Test Cases of Smoke Test is a part of Regression testing is obtained from

 Regression Testing and covers only functional specification or Software
. the core functionalities. Requirement Specification (SRS).

04 Smoke tests are performed by the Regression tests are performed by the
. developers. professional testers.

Smoke tests are performed quickly Regression tests are not accountable
05 to confirm whether to accept or for accepting or rejecting a software
. reject the build. build for further testing procedures.

07 Cost of Regression testing is little bit

. Cost of Smoke testing is low. high.

08 This testing isd ocumented or This testing is not documented or

. scripted. scripted.

09 It is also know as Build Verification

. Testing. It is not known by any other name.

10 Requirement of time and manpower Requirement of time and manpower is

. is less than Regression Testing. less more than Smoke Testing.

Smoke Testing Vs Sanity Testing – Key Differences

Following is the difference between Sanity and Smoke testing:

Smoke Testing Sanity Testing

Smoke Testing is performed to ascertain that the Sanity Testing is done to check the new
critical functionalities of the program is working fine functionality/bugs have been fixed

The objective of this testing is to verify the “stability” The objective of the testing is to verify the
of the system in order to proceed with more rigorous the system in order to proceed with more
testing testing

Sanity testing in software testing is usuall

This testing is performed by the developers or testers
testers

Sanity testing is usually not documented a

Smoke testing is usually documented or scripted
unscripted

Smoke testing is a subset of Acceptance testing Sanity testing is a subset of Regression Te

Smoke testing exercises the entire system from end to Sanity testing exercises only the particula
end the entire system

Smoke testing is like General Health Check Up Sanity Testing is like specialized health ch