How IoT is changing our Lives
This paper provides an overview of the Internet of Things (IoT). It gives information how IoT is changing our lives in different fields. It gives brief information for applications in media, environmental monitoring, tag devices, energy management, medical and healthcare fields.
How IoT is improving our life and adding the accuracy and flexibility. This paper highlights the major areas where we are directly or indirectly using IoT enabled applications. How current revolution in Internet, mobile, and machine-to-machine (M2M) technologies can be seen as the first phase of the IoT.This paper also highlights the Enabling Technologies for the IoT and given the information about the technologies widely used in today’s mobile phones
Outline/structure of the Session
What is IoT?
IoT Extends Internet Connectivity
IoT - Major areas where we are using applications
Extending the IoT Area…
Enabling Technologies for the IoT
Knowledge about IoT and related applications
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Archana Sridhar - Automation Testing with Devops in Agile methodolgy
What is DevOps?
DevOps – a portmanteau of Development & Operations – is a software development methodology which looks to integrate all the software development functions from development to operations within the same cycle.
This calls for higher level of coordination within the various stakeholders in the software development process (namely Development, QA & Operations).
Devops is not a tool, it’s not a methodology, but it’s a process of integrating software development and quality. Devops is not release management system, it integrates with release management system by standardizing the process.
Traditional Development teams and Operations departments normally have completely different motivations and deliverables. Development keeps changing things based on user or market demands for new features (and fixes of existing features). Operations try to keep everything as constant as possible in order to deliver maximum availability and stability of software services. These two contradicting goals create a bottleneck when it comes to delivery of business value.
Why DevOps: Automated Deployment
Most companies are adopting this Devops model in order to facilitate a practice of automated software deployment. DevOps provides the structure that enables teams to push software out as a service on a weekly, or daily, or even hourly basis. The traditional concept of a “software releases” transforms into a continuous cycle of service improvement.
DevOps is a logical evolution in removing all the obstacles to getting high-quality software in the hands of customers. It smoothens the process for agile development and continuous integration, automating the process makes it easier, is more transparent and leads to higher quality.
Beyond Functional Testing: Automation for Load Testing, Stress Testing, and Performance Testing
As processes are maturing and Devops is moving at high speed, you may want to integrate performance testing, stress tests and load tests along with it. It’s about creating a continuous process to both check and monitor the software services.
Once the processes are mature and stable enough to be moved to Devops, functional testing can be integrated with load, stress and performance, to continuously integrate with the process to aid more control and structured way of operation. Performance tests can be integrated to check the performance over a period of time on real time data rather than idealistic data. Similarly load and stress can be tested over a period of time.
Devops in Real world
DevOps practices promise bridge all communication gaps that usually exist between software engineers, IT, QA and other parts of the business. DevOps should create complete transparency within the business to facilitate agile planning and prompt decision-making. So, as the organization integrates DevOps, it makes services continuous.
DevOps projects must identify and align with business needs, it always ask why you're taking up a DevOps approach and what success will look like. DevOps specific goal will be to shorten the cycle to fix bugs or grapple with fewer bugs in each new release, improving customer retention.
Devops and Cloud computing
DevOps developers successfully use private or public cloud to create more complex environments that simulate production use for version testing. The scalable, self-service nature of cloud computing allows developers to provision and migrate new versions for testing with little -- if any -- reliance on IT administrators. This makes testing faster and simpler than traditional provisioning requests to IT.
Public cloud is usually preferable because it offers high scalability and self-service without any danger of exhausting local IT resources. When testing is complete, the public cloud resources can be released to save money until the next testing cycle starts.
Approach for Integrating Devops and Automated Testing in cloud
Step 1: Get proper Test automation in place
Since a key aspect of DevOps is to ensure that deployments are made continuously, as well as effectively, the need to for having tests in place is pretty obvious – untested and faulty code has the potential to mitigate the benefits of DevOps.
Step 2: Choosing the right CI Integration and integrating it
Integrating the automation suite with a build deployment tool to enable centralized execution and reporting.
Step 3: Making customizations as requirements for organization and cloud integration
The customizations made can be pertaining to code and testing framework, to check mode of reporting, environment availability. The integrations related to cloud must be made.
Step 4: Monitoring Results
We can also use a small subset of existing high priority test cases to be executed periodically on production to actively monitor the environment.
Challenges in implementing Devops
- The organization processes and practices must be matured enough for Devops.
- Exploratory or ad-hoc testing may at first appear to have no room in DevOps.
- DevOps is still a relatively young method, partly experimental, so support is solely dependent on internet.
References & Appendix
Archana Krushnan is currently working as Test Analyst at Nihilent Technologies Pvt Ltd. She has been in the field of Software Testing for 5.5 years and worked on several domains such as Telecom, Ecommerce and Healthcare. Her interests include exploring new things in testing and sharing on her blog. She has previous experiences of working with companies like Reliance Communications Ltd and Fab.com. She has good knowledge in Selenium, Jmeter and Soap UI. She is ISTQB Foundation Level Certified.
madhavi / YogeSh Karanje - Understanding Agile IterationmadhaviSr. Test AnalystNihilent TechnologiesYogeSh KaranjeTest LeadNihilent Technologies
schedule 1 year agoSold Out!
The heartbeat of Agile development is the iteration – the ability of the team to create working, tested, value delivered code in a short time box – with the goal of producing an increment of potentially shippable code at the end of each iteration. This is a significant challenge for the team, and mastering this skill takes guidance and practice. This white paper describes the basic iteration pattern and the activities that a team engages in to meet this key challenge.
Archana Sridhar - Exploratory Testing explored using Risk Analysis for Mobile Applications
Exploratory testing is an approach that can be described as simultaneous learning, test design and test execution. It is testing parallel with learning. We all consciously or un-consciously do exploratory testing. We use the concept of “Think Different” every time we do exploratory testing. Creative exploratory tests help to break the monotonous scripted testing and bring out newer test case each time.
This paper brings out the approach of exploratory testing which is an emerging topic and clubbed with risk based analysis brings a powerful approach to testing. Today’s fast growing technology and rapid changes in projects, makes exploratory testing an important approach for every tester. Scripted testing alone often fails to find hidden defects. Exploratory testing, however, can expose these risks because it incorporates exploration and experience into the testing process.
One common misconception about exploratory testing is, it is unstructured, and this paper tries to showcase the concept of doing exploratory testing with risk analysis and gives it a more structured approach.
Also this paper highlights exploratory testing in mobile applications, using risk analysis. Mobile application testing embeds a lot of features, navigation flows, OS, device dependency. Mobile testing always requires an investigative approach apart from the fundamental test approaches. Exploratory testing with risk analysis makes a mobile testing much structured and easier to delve deep into the application and find bugs.
Archana Sridhar - Continuous Integration with BDD for faster and quality release in Agile
This paper is to elaborate the concept of Behaviour Driven Development (BDD) with the help of Cucumber approach and how it will be useful in testing. This testing technique collaborates with both Testers and Business objectives. It can be applied to all testing levels and can be executed by all users. Main objective of this approach is to make tests easier to read and execute. Tests if easily readable can be execute by business users and they can get user friendly reports without much hassle of understanding and executing code.
BDD approach basically focuses on the user and how system responds. BDD integrated with CI(Continuous Integration tool) can be very beneficial to fast paced projects, very common these days.BDD and CI approach together will bring development practices and performance, alignment with the business, measurement, effectiveness, efficiency, and non-learning solutions all together this solution if implemented can work and deliver exceptional results.
BDD uses examples in conversation to illustrate behaviour and is therefore very useful in helping clarify requirements. Good BDD frameworks we can reduce regression test cycles, saving you time and money. Successful BDD means there is the potential to deliver defect-free software at point of release which operates as expected with reduced complexity