Cloud Testing Research

MOBILE DEVICE MANAGEMENT WITH INTERNAL 1
`
Mobile Device Management with an Internal Device Cloud
Krishna Sriharsha Maramganti
Illinois Institute of Technology
Information Technology and Management
School of Applied Technology
Chicago-60616

MOBILE DEVICE MANAGEMENT WITH INTERNAL DEVICE CLOUD 2
Table of Contents
Abstract……………………………………………………………………………………………3
Conventional software testing lifecycle and mechanism………………………………………….4
Software testing lifecycle …………………………………………………………………………6
Cloud Testing……………………………………………………………………………………...9
Testing mobile devices using device cloud……………………………………………………...15

ABSTRACT
Software Testing is the one of the very important phases of Software Development Life Cycle.
Software Testing can be mostly implemented at any time during the Software Development Life
cycle. But typically, most of the testing is done only after the Requirement Phase is completed and
the coding process is done. The main issues with the Conventional Testing is that it usually requires
lot of expensive Infrastructure and resources. As the business Requirements are growing every
single day, it is very difficult to create real time Testing Environments which requires lot of
Infrastructure and Resources. This raises the concept of Testing in Cloud Environment which
provides unlimited resources with scalability, Flexibility and open to distributed Environment. The
main advantage of cloud based testing is that it reduces the time and indeed leads to cost effective
solutions. This Research paper gives also gives a detailed study of handling security challenges of
mobile devices and Apps using “DeviceConnect”, a “Private mobile device cloud”. DeviceConect
is an internal cloud based mobile application testing platform which provides the best management
experience of mobile application testing assets. This paper also gives clear analysis of how Cloud
based Testing is successful implemented using DeviceConnect.
Keywords: DeviceConnect, Testing in Cloud, Software Development Life Cycle

Software Testing which is one of the significant activities of a software development
life cycle, helps in determining the correctness, completeness and quality of any software product.
Generally, Software testing is done through the Infrastructure that exists in-house within the
organization.
From the past couple of years, as the technological changes going on enhancing to a greater extent,
the software testing function became a challenging activity due to the increase in resource
requirements, increase of cost, requirement of high end infrastructure. Due to this growing
demands and needs of Software testing, it became very complicated task to maintain the high end
in-house infrastructure and testing facilities that mimic real-time environments. The Cloud
Computing had opened up wide range of advancements in today’s typical technological world
which indeed helping the Software testing to a greater extent in providing one of its services called
“Infrastructure as a Service” by providing on-demand flexibility like “Pay as you go”, greater
levels of efficiency, cost determination factors etc. With the cloud based testing organizations need
not to be worried about wasting time in finding servers, licenses, Testing tools and Installing and
configuring them all the time. Cloud Service providers give access to the scalable and ready to use
virtual environments with a stack of operating systems, test management, execution tools,
middleware and finally the storage required to create the test environment that closely resembles
the real time environment. Testers can run the existing applications and virtual machines with
utilized pool of virtualized infrastructure to scale up the test environment within minutes.
Time-Market is often restricted by traditional test environments because time consumption of
creating on Premise Test Environments. It is basically taking weeks and months just to set up a
simple test Environment for a single user based application. This is making the project deadlines
tight, indeed making failure of projects. This Cloud Based Testing technique brings up the concept

of in-built resource features in cloud indeed speeding up the project time. It helps the organizations
use the resources as they need and pay as they go. Reducing the burden of buying servers,
Reducing the effort of installing Software’s to test are some of the special features of Cloud Based
Testing.
2.CONVENTIONAL SOFTWARE TESTING LIFE CYCLE AND MECHANISM
Software testing is a set of planned activities which follows a set of cycle which are inter-
connected with one another. A simple mode of software testing life cycle consists of set of
phases starting from Requirement Analysis to maintenance phase. This process model is highly
simplistic and most believed model in software industry. This Software Process model helps us
to simulate the testing process in a convenient way. The phases which involved in conventional
Software Testing are as follows:
Feasibility Analysis: A deep analysis phase where the economic and technical feasibility of the
development project is deeply assessed to determine whether to move on with the project, within
a given budget, schedule.
Requirement Analysis: The most difficult and very important phase in software testing, is the
Requirement Analysis phase where we gather Business Requirements which are needed for the
success of the project. It is very important phase which determines the Scope, Cost Values of
users, Functional Requirements, Non Functional Requirements etc. The requirements gathering
engineer should make sure that he should be involved in gathering requirements by identifying
correct stakeholders, gathering exact domain knowledge, Identifying the required regulations and
laws, identifying the possible ambiguities, resolving negotiations, gaps in business markets and
validation of required requirements.

Product Architecture: The phase of Product Architecture involves, determining the
Components of Product, Determining the best possible communication mechanism, work flow
designs, Coordination between each component of the product, Data Sharing Architecture etc.
Programming: This is more of Implementation phase which is being carried out by large
number of programmers. Each Programmer handles number of different tasks and later on
integrates all the tasks at the end performed by each of them. This phase is verified by “Unit
Testing” where each and every component (unit) is tested separately.
System Integration: Once each and every unit are designed, the total system is kept together
and been Tested as a part of Integration testing. It is called as Integration testing because, it tests
each and every unit of the system. This phase is also used to carry out another phase of testing
known as Reliability Testing where the removal of fault is estimated by the Reliability growth
till the targeted reliability is reached.
Delivery: Once the Integration testing is done we will be going with the delivery phase where
the User Acceptance Testing is carried on. This Delivery phase also highlights another form of
testing called as Certification Testing.
Operational Maintenance: If there was any change in software requirements or if there is
failure in any component of a product then the operation of maintenance is initiated. Testing
should be made right after the operational Maintenance phase. It is advisable to test the
components for which the Maintenance had done.
The below figure shows the Testing phases which occurs at each phase of Software Testing Life
Cycle.

Software Testing Life Cycle:
To ensure the proper quality goals, we need to define some set of processes in the testing phase
of software development lifecycle. We call these phases of testing as Software Testing Life
cycle. Software Testing Lifecycle activities are the planned activities which with each of them
with a different goals and deliverables. Below are the phases of “Convention Software Testing
Life Cycle phases”
 Requirement Analysis
 Test Planning
 Test Case Development
 Environment Setup
 Test Execution

 Test Cycle Closure.
Requirement Analysis: During this phase, team studies the requirements of testing in reference
to the designed system or product. The quality Analyst team is responsible in interacting with
clients, Business analysts, Architects, leads etc. to get the requirements in detail aspects. The
Activities usually involve
 Tests Identification
 Technical and Operational Feasibility of a system
 Identifying the environment in which testing is to be performed.
 Articulating Requirements.
Test Planning: A strategy phase where typically all the team will sit together, conduct meetings
and design a test driven document which helps in estimation of cost and effort which is required
for the success of the Testing phase. A systematic schedule is prepared with the help of Team
Manager and Team Leads. Following are the activities which comes under test planning:
 Preparing a Test Plan and a Strategy Document
 Selection of Tool and Estimation of effort.
 Determining roles and responsibilities with the help of Test Leads and Managers.
Test Case Development: This phase mainly involves creation of Test cases using the test data
and test requirement Specification Document. A proper review is made after the creation of test
cases and test data document. Following below are the activities which come under Test Case
Creation:
 Creation of test cases
 Creation of Test Data Document
 Review of Test Cases

Test Environment: One of the critical phases of Testing, which decides the software
environment which the product needed to be tested. The suitable Hardware and Software aspects
are taken into consideration and final decision analysis is taken to decide the best possible
Environment which the product needed to be tested. Following are the activities which come
under this phase
 Getting Insights of Architecture
 Software and Hardware document list for Environment Setup
 Smoke Test.
Test Execution: All the test cases and Test Scenarios are taken into consideration and final
execution is done basing on them. Bugs or Defects are reported to the programmer. The
programmer verifies the bugs or defects and tries to review the code and later it was re-sent to
tester for re-execution. This cycle continues and the process is repetitive till the customer
satisfaction is obtained. Following are the activates which are involved in Test Execution phase:
 Execution of Test Plans
 Defects/Bugs Detection
 Re-Testing
 Communication between testers and Developers.
Test Cycle Closure: After the Testing Implementation is done, all the testing team including
Managers, Leads, Quality Analysts etc. will assemble at a single place to draw out the
conclusions from the project and try to make some future plans. They will try to analyze the
things which had taken place throughout the life cycle and try to avoid the mistakes made during
these phases for the next project. The following below activities are performed during the testing
Closure:

 Test Report
 Test Analysis Document
 Feedback Reports
 Test Metrics.
Image Reference: International Journal of Scientific & Engineering Research, Volume 3,
Issue 9, Spetember-2012 2 ISSN 2229-5518.
Cloud Testing
Cloud Testing uses the Concept of Cloud computing which helps to provide the share resources
as the form of pay as you go and eliminates the upfront costs of servers as the concept of server
management is being carried out by the Cloud. The concept of software as a service in cloud will
help the companies to get the licensed versions of software’s which are highly secured and
reliable. The Cloud Service of Platform as a service will help organizations to provide a platform

which helps people to develop, run and manage complex applications( both software and test
applications) without any complexity. Infrastructure as a Service will help organizations to
provide Infrastructure like servers, Cpu’s , Testing Environments etc. without any interruptions.
The main advantage of migrating to Cloud is even the Security will be handled by Cloud Service
Providers.
The cloud usually classified into Private, Public and Hybrid in nature. Cloud nature is
differentiated depending on the data security which we need to opt for.
Public Cloud: All the services in the public cloud are provided through internet. We can call the
Public cloud as nothing but the Internet where the service providers like amazon , google ,
Microsoft use internet to make resources like applications , storage etc. The main advantage of
public clouds are they provide high user experience and are very less expensive to set up.
Disadvantage of using the Public Cloud is that it limits the configurations, security and other
aspects making less ideal for the enterprise organizations.
Private Cloud: Private clouds are basically completely handled by one single company. Private
clouds are not an options for the medium scale companies and are being used by hugest
enterprises. Bothering of Security and Firewalls are always a big concern for it.
Hybrid Cloud: As the name suggests it is more off a combination of both public and private
cloud. The ability for the disaster recovery is the main advantage of the hybrid cloud.

Image Reference: www.oracle .com
Life Cycle of Cloud Testing:
Cloud Testing which became very predominate in today’s Information technology world has its
own life cycle like software development life cycle. The phases of cloud testing are as follows:
1) Develop the User Scenarios
2) Design Test Cases
3) Select Cloud Service Provider
4) Setup Infrastructure
5) Leverage Cloud Servers
6) Start Testing
7) Monitor Testing Goals

8) Deliver Results
 Develop User Scenarios:
 The first phase is developing the user scenarios where the quality assurance analyst will
develop the user based scenarios. User Scenarios are those which are the stories which
are taken from the hypothetical system taking a complex problem into consideration.
 Test Cases:
 The second phase is to design all the possible test cases taking user scenarios into
consideration. A test case acts as an initial point of the test execution which composes of
test data, preconditions, expected results, test scenarios etc. Every Test case has its own
parameters such as Test id, Test Scenarios, Test Case Descriptions, Test Data, Test
Parameters, Actual Result, Environment Information etc.
 Select Cloud Service Provider:
 Cloud Service Providers are the trusted third parties which provide cloud Services to
other organizations. Cloud Services as we have discussed before include, Software as a

Service, Platform As a Service, Infrastructure as a Service. The organizations which are
availing the Cloud Computing as a Service should make sure that they are getting it from
the trusted third parties as Security is a huge concern in Cloud. When we are having
Cloud as a Service, the data of other organization is handled by other third parties. So
Organizations should take that they avail trusted cloud services from trusted
organizations.
 Some of the reliable cloud providers are Amazon, Microsoft which have Amazon web
services and Microsoft Azure as their Cloud Services.
 Setup Infrastructure:
 The main Advantage of Cloud as a service is to avail the Infrastructure as a service. We
need to make sure that we need to set up all the required Infrastructure which is required
for the testing environment before and need to make the configurations in the cloud
accordingly. Pay as you go service will help to scale up the Servers and other
Infrastructures whenever we need with extra payment as you go front.
 Leverage Cloud Servers:
 We do not need to set up or establish our own servers with huge amount of costs and
Infrastructure. Cloud helps us to provide inbuilt Server’s where we can leverage those
servers as we go up-front with paying the amount required for each scaling up of server.
The main advantage is that; you do not need to take of Maintenance part as it is taken
care by the cloud service provider.
 Start Testing:
 After setting up everything we need to start up the testing process by taking the Cloud
Technology assistance. All your environment is already got set up in the cloud. We need

to test it according to the requirement documentation and make a summary report
towards the end.
 Monitor Testing goals:
 After testing has done in the cloud, we have to make sure that we need to monitor the
goals analyzing whether we had reached all the required goals or not. We need to start
verifying the software requirement specification document and we need to make sure that
we have reached all the goals of testing or not.
 Deliver Results:
Final Phase is to deliver the test results to the Programmers where the programmers will correct
all the defects which are been showcased by the testers and they will resubmit the results back to
the tester again. Testers will retest it back again and deliver to go signal to the programmer
saying to release the product to the market. Then Programmers will release the product / system
into the market.

TESTING MOBILE DEVICES IN CLOUD USING DEVICE CONNECT:
Private Mobile Device Cloud:
Every single day lot of organizations start publishing lot of mobile applications. Mobile Devices
have become so much dominant for all the customer facing in this B2B world. Even though the
advent of mobility brought the enormous flexibility to the world, the massive device types made
it complicated to find a best possible method to make mobile testing possible. The Advent of
Mobile Technology is making number of companies to start developing number of mobile
applications so that users can use them on their mobile gadgets flexibly. As the advent of
development of mobile Applications are getting increased every single day, the need for the best
flexible testing Environment is also being increased on day by day basis. As the Organizations
started growing throughout the world each organization has its team wide spread across different
global locations. Testing teams are facing the problems to buy multiple mobile device at multiple
locations and start testing at multiple locations. As the amount of mobile platforms increased,
there started requirement of number of test cases, so much of time which should be given by
tester on it, very huge amount of cost kept on bothering the testing team. The quality of an app is
directly proportional to the number of devices we have tested, which is told by the “Infosys”. A
huge communication gap is being built between testing team at one location to the testing team
location at different global location. The main issues came when a single pool of mobile devices
should be shared in different global locations. There started a communication gap as the
organizations which are located globally are unable to access to the pool set of resources which
are located at one particular local location. Another Concern is that, some mobile devices are

being unused, some are stolen, some are prone to risks etc. making the testing budget out of
schedule and also added expenses. The major challenge faced by the testing team is that how can
they test on sufficient number of devices to make sure that users do not land into problems. The
question rises how can we eliminate this issue. DeviceConnect is a Private device Cloud which
helps to eliminate all these challenges quite easily.
DeviceConnect will help people in accessing pool of mobile devices anywhere through out of the
world using Cloud Service without any concerns with the security. DeviceConnect will solve all
the above concerns without any Performance issues or any External Risks like loosing of mobile
device, damaging of devices etc. DeviceConnect will help you to secure up-to 48 devices at a
same time without any security concerns. DeviceConncet will help us in providing the secure
and authorized remote access to access all the shared pool of mobiles which are location at a
single location. It will help in Manual and Automated mobile App testing in a more secured
manner.
The main advantage of DeviceConnect is, it reduces the cost of Testing each and every mobile
device, do not need to buy multiple devices, quality improvement of mobile websites, Security
and enhances efficiency.

Managing Automated Testing and Manual Testing using DeviceConnect.
Whatever testing you perform, either Automated or Manual Testing, DeviceConnect will help
you to make it done without any complexity. We know that when the organization is getting
spread globally, it is very tough for all the testers who are spread globally from the same
organization to know which mobile devices are used by which tester. DeviceConnect will also
help the users to administrator and monitor mobile inventory and usage.
For doing the automation testing, DeviceConnect uses Mobile Labs Trust a mobile application
testing software, to perform the automation testing. This software is being installed on the
devices to perform the automation testing which tests almost all the devices which include
Android, IOS, Tablets and other devices.

The Above diagram shows the screenshot of the automation testing which is done by using the
DeviceConnect. After Installing the software, the users can select their own devices which can be
Android, IOS, Blackberry, Windows. After the automation is done then an executive summary is
being generated with Test Name, Results, the Time Zone, The Starting date and Ending Date
with appropriate time schedules, Host Names, The Product Versions and the Operating Systems.

DevieConnect will help in supporting number of remote gestures which includes scrolling,
dragging and selecting. Device Rotation can be done quite easily using DeviceConnect. The
following things you can do with the DeviceConnect:
 24*7 Access to all the teams which are located at the different parts of the countries for
the same organization.
 Access of IOS, Android, Blackberry and all other devices using the same Device.
 Communication is very secured and the data between communication system is in
Encrypted format.
 Utilizes HPUFT in running fully automated tests.
 Helps and supported all the testing team in troubleshooting.
 Provides Flexible access of the devices.
DeviceConnect will also help to make Manual and Automated Website testing. Now-a-days most
of the organizations are migrating towards the mobile website technology which are built in in
HTML5. To make the mobile websites more interactive and to provide the websites with global
experiences, mobile testing with human users is more importantly required. The human

interaction became very important factor in each and everything right from testing mobile
websites to defect tracking and measuring efficiencies. With the advent of deviceCloud made it
possible perform the gestures remotely and monitor the key aspects of the website using the
inbuilt monitoring system which is available in the DeviceConnect.
Test Your Way Strategy by DeviceConncet:
Device Connect as a main and central component it provides Management, Inventory, The
Management of Schedules and other application maintenance. The deviceConnect strategy for
Enterprise will provide the automated and manual testing solution by the same application
software device. The offerings of automation are handled by the Mobil Labs.
Device Connect Cloud Architecture and Cloud Security Architecture
When compared to all the public offerings the device connect provides the best and superior
security. The DeviceConnect is installed behind the corporate firewall. It does not require any
wide area network connection. It was mainly designed for isolate Wi-Fi networks from internal
LAN connections. Most of the communication with the device are made with the wired
connection. The deviceConnect Server is being connect from the LAN of Desktop to the devices.
All the devices need to be have to apply on the same subnet as the internal LAN and we can take
the help of proxy servers for the routing.
Remote Device Control: The user has the control of same device screen wherever he is located in
the world. The hardware side of the DeviceConnect is very simple and elegant since most of the
most of the functionalities are performed by the Mobile Labs.
References

Jorgensen, P. C. (n.d.). Software Testing: A Craftsman’s Approach, Fourth Edition. Auerbach
Publications .
Mili, A. (2012). Software Testing: Concepts and Operations (Quantitative Software Engineering
Series. WILEY.
Vanitha. (n.d.). conventional software testing vs cloud testing. Retrieved from
http://www.ijser.org/researchpaper/Conventional-Software-Testing-Vs-Cloud-
Testing.pdf

Cloud Testing Research

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to Cloud Testing Research (20)

Cloud Testing Research