Testing of desktop and web apps

1
Testing of desktop, web and mobile applications
2

• Desktop
• Desktop applications
• Testing approaches
• Web
• Web services
• REST
• API testing
• Mobile
• Types of mobile apps
• Testing approaches

3
Desktop applications
By definition, a desktop application means any
software that can be installed on a single
computer (laptop or a desktop) and used to
perform specific tasks.
4
Desktop applications
5
Areas that needs to be tested
6
GUI Testing
7
Functional testing

• Workflows, functions, links etc.
• Warning messages
• Resolution change effect on the application
• Theme change
• Print
• Installation Testing (Upgrade/Downgrade/Uninstall)
  
• Testing with multiple user accounts
• Sleep mode
• Cache

8
Compatibility testing
9
Performance testing

• Long period of continuous use
• Memory
• Generate Power Efficiency Diagnostics Report

10
Web services
A Web service is a service offered by an
electronic device to another electronic device,
communicating with each other via the World Wide
Web.
11
SOAP web services
SOAP (Simple Object Access Protocol) is a
protocol specification for exchanging structured
information in the implementation of web services
in computer networks. It uses XML Information Set
for its message format, and relies on application
layer protocols, most often Hypertext Transfer
Protocol (HTTP) or Simple Mail Transfer Protocol
(SMTP), for message negotiation and transmission.
12
RESTful web services
REST stands for REpresentational State Transfer.
REST is web standards based architecture and uses
HTTP Protocol for data communication. It revolves
around resource where every component is a
resource and a resource is accessed by a common
interface using HTTP standard methods
13
API testing
Application program interface (API) is a set of
routines, protocols, and tools for building
software applications.
14
API testing

• Test cases of API testing are based on
• Return value based on input condition it is
  relatively easy to test, as input can be defined
  and results can be authenticated
• Does not return anything When there is no return
  value, behavior of API on the system to be
  checked
• Trigger some other API/event/interrupt If output
  of an API triggers some event or interrupt, then
  those events and interrupt listeners should be
  tracked
• Update data structure Updating data structure
  will have some outcome or effect on the system,
  and that should be authenticated
• Modify certain resources If API call modifies
  some resources then it should be validated by
  accessing respective resources

15
API testing