Gamification at work is an emerging trend in the corporate world. Games and work were considered antonyms in the past, but now both of these coexist in many organizations. The current generation workforce has grown up with video games. Gen Y employees want to achieve more, engage in multiple concurrent activities, prove their skills and get quick recognition. All these are characteristics of playing a game.
This will take the audience through what gamification is, why gamification should be considered at the workplace and how it is relevant to testing. It also provides sample games that can be used for various testing activities, how to define scoring strategy, difficulty levels that will engage the team to be interested in ‘gamification’‚ how to redeem rewards for tangible benefits and the constraints of successful gamification. At the end of the session, there is a case study of gamification for one of the testing activities. This provides insights into:
• Introduction to the concept of gamification
• Why gamification should be introduced at work
• How to implement gamification in testing
• Go through a case study
• Understanding the gamification concept
• Learn how to approach gamification in testing
• Get an overview on implementation
• Get sample games that can be applied for testing activities
• Learn the Do’s and Don’ts in gamification
The Internet of Things (IoT, also Cloud of Things or CoT) refers to the interconnection of uniquely identifiable embedded computing – like devices within the existing Internet infrastructure.
An unprecedented number of devices are being connected to the internet and each other to provide useful information and guidance in our daily lives (Refrigerator, TV, Mobile, Tablet, Lighting, Energy Meters, to name a few). Each of these devices has its own computing power embedded within itself. We will be looking at one such device which is a Digital Set-Top-Box. The Set Top Box has become the central component of the home entertainment hub, and can take inputs from multiple sources, which it converts into signals for the TV.
So, how do you test such an IoT device? It is different from testing an application. In an embedded product the software is made in different parts and it works together as a system. The function of the product depends on the successful interaction between various software and hardware modules like Operating System, Drivers, Middleware, Application, and the Physical inputs and outputs. We will be looking into the world of Digital TV and how testing happens in this complicated environment .We will focus on the Set-Top-Box, where we depend on the hardware to test and the output is on the TV. Unlike in typical application testing where we can run the software on the devices and test, we also need to focus on the Audio and Video quality, which has its own challenges.
• Overview of Digital Pay TV Technology
• Test environment setup challenges and solutions
• Test Process and Best Practices
• Non-Functional Testing – Why it is important
• Test Automation – How it helps
In today’s technologically advanced world, it has become imperative to be in constant contact with customers – even when they are on the move. Mobile usage is increasing, and interestingly, more and more people are using their mobiles to browse sites and buy products. According to a recent study, the total number of mobile users is expected to reach 5 billion by 2017; mobile internet usage will surpass desktop internet usage for personal use.
In light of these statistics, every business, in order to survive, will have to reach out to its customers through the mobile. But mobile phones have their own limitations – display sizes vary with device; the market is shared across multiple operating systems; RAM and CPU constraints; networks used that have much lower bandwidth, etc.
The challenge arises because mobile users don’t approve of these limitations and expect the faster or same response from websites accessed over their mobiles. Hence the need for performance testing on mobile device becomes even more critical than on a the desktop. The performance testing on mobile needs to focus on back-end as well as front-end performance. This will throw light on performance challenges for different types of mobile apps; tools & techniques that can be used to find performance issues and recommendations to address them.
• Why mobile performance testing
• How mobile performance testing is done
• Tools & techniques used for mobile performance testing
• Recommendations for a better user experience on mobile device
Many businesses are migrating their data, infrastructure and applications to the public cloud. The immediate advantage of being in the cloud is of saving on all the capital expenditure. To top that not having to deal with the hassle of un-interrupted power and bandwidth you get a pretty compelling argument for doing so. While all these advantages are great, but by moving proprietary data to the cloud without adequate testing, does leave enterprises open to attacks and other procedural failures.
We will look at what does it mean for security testing when it comes to data and infrastructures being the cloud. Additionally what are the tools, techniques and procedures to do security testing for cloud based information assets. We will end with a comparison of the various public cloud vendors focusing on their security posture and how we can leverage those to protect our assets.
• Agile requires cross boundary skills and quick resolution
• Technology is fast changing
• Look at the design considerations/limitations rather than nag for a low priority defect
• Unearth design flaws early in the development cycle
• Work towards minimizing defects rather than maximizing defects
• Learn about security testing in the cloud.
• Understand the differences in public cloud vendors and their security offerings.
• Get a simple 10 step process for auditing and/or hardening information assets in the cloud.
• By the time the workshop is over you will be confident about your choices for cloud security and assured about how you would like to proceed
Dev/Ops, continuous delivery, mobile, cloud and the Internet of Things is forcing a rapid pace of development. The agile software development process has meant a reorganization of teams and the skill set of testers is evolving. Now, QA professionals and business analysts are more ingrained in the overall development process from start to finish.
A “shift–left” approach is being adopted where testing is done as early as possible in the development lifecycle. This requires test automation to be integral part of continuous integration and more testing carried out on the API and web service layers. As API integrations between multiple systems become more common, provisioning an end to end test environment is becoming prone to delays.
“Shift–left” approach affirms that any delays in setting up test environments due to service dependencies be mitigated by virtualizing those services
- The new HP Lean FT solution for the ‘DevTester’
- API and web services testing early in the development lifecycle
- Best practices for test automation in Agile and continuous testing processes
- Service Virtualization for removing test environment dependencies
Now a days the software development life cycle needs aggressive regression testing.
You can see there is quite good differences we have between test specification and test plan
Testing Ejbs requires a container which gives all the required conditions to deploy and use the deployed bean. OpenEjb is open source frame work which can be used to test all the business methods.
Etl testing is testing the transformation done of source data before moving it to the target and also validating the target data.