2017 Edition

We will discuss the importance to verify security flaws and how security activities can be done during functional testing. Testers should have security knowledge, that can be applied with the business logic of the solution, to detect potential security problems and minimize vulnerabilities.

This workshop delves into the planning of Testing projects and the definition of achievable objectives for the success of the project. Going through different methodologies (from the Standard Plan to new agile proposals that have gained popularity in recent years), attendees will learn to create an Effective Plan. This workshop provides valuable tools for those who are responsible for managing Testing activities. Whether it’s a short project or a complex one,Testing is incorporated at the beginning of the project or at the end: a good plan is always necessary.

With the growth of APIs in the software industry we are forced to perform a lot of tests in less time, which are easy to maintain. Under these premises I found Chakram to facilitate the work we need to perform.

Chakram allow us to test the APIs Rest in a simple and quick way. This framework gives us as an advantage:

• Perform HTTP Assertions based on Chai.js
• Fully exploits javascript promises
• Use BDD + Hooks
• Extensible, allows new assertions to be added to the framework

The workshop is focused on getting to know the framework, giving the main guidelines of how it works and creating the test in a simple way.

Attributes of quality such as portability, reliability, are especially difficult to test and more so to automatize. The diversity of devices, operating systems and versions of these operating systems usually limits the amount of devices on which the software testing can guarantee operation.

Xamarin Test Cloud technology allows the automatization of test cases on thousands of mobile devices to be executed simultaneously. Obtaining thus the possibility to observe the behaviour of the system while in different environments.

In this workshop we present the motivation for the automatization process in the case of non functional attributes of quality. We also present a practical example in Xamarin Test Cloud.

Requirements:

• The participant must bring laptop with Windows operating system.
• Visual Studio 2016 and Xamarin are required. To install see the following tutorial and check
  • https://developer.xamarin.com/guides/android/getting_started/installation/windows/manual_installation/#Installing_Java_SDK_JDK
  • Verify the Path of the SDK of Android
  • Verify the Path of Java
  • Install Java 7 (Dic 2012): http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
• To be able to execute the automatization during the workshop the following images must be downloaded from the emulator:
  • https://github.com/ludei/cocoonjs-cli/wiki/How-to-solve-the-compilation-error:-%E2%80%9CUnable-to-resolve-project-target-‘Google-Inc.:Google-APIs:19’%E2%80%9D
  • https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/debug-on-emulator/android-sdk-emulator/

We will discuss the importance to verify security flaws and how security activities can be done during functional testing. Testers should have security knowledge, that can be applied with the business logic of the solution, to detect potential security problems and minimize vulnerabilities.

Agile dev teams seek to develop testing skill in all team members, so they have at least a minimal knowledge of the testing activities. Testers also want to deepen their skills.

How can we distribute and create that knowledge?

Test Information Capsules allows a team to incrementally develop skills, building it from the team experience and from case studies. Capsules serve as guides for learning circles (for the whole team) and communities of practice (to those specialized in testing). The capsules are used in 30-60 min sessions: a concept is presented, it is applied to a case study and then extended to the team current project.

We present some capsules: Automatic test architecture, Test data, Page objects, Oracle model and Diagnostic tests.

We close with new capsules generated by the participants.

The following organizations CADI, Forge, Integrity, Nahual will provide information about their work and how you can access their courses.

Xamarin Test Cloud technology allows the automatization of test cases on thousands of mobile devices to be executed simultaneously. Obtaining thus the possibility to observe the behaviour of the system while in different environments.

In this workshop we present the motivation for the automatization process in the case of non functional attributes of quality. We also present a practical example in Xamarin Test Cloud.

Requirements:

• The participant must bring laptop with Windows operating system.
• Visual Studio 2016 and Xamarin are required. To install see the following tutorial and check
  • https://developer.xamarin.com/guides/android/getting_started/installation/windows/manual_installation/#Installing_Java_SDK_JDK
  • Verify the Path of the SDK of Android
  • Verify the Path of Java
  • Install Java 7 (Dic 2012): http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html
• To be able to execute the automatization during the workshop the following images must be downloaded from the emulator:
  • https://github.com/ludei/cocoonjs-cli/wiki/How-to-solve-the-compilation-error:-%E2%80%9CUnable-to-resolve-project-target-‘Google-Inc.:Google-APIs:19’%E2%80%9D
  • https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/debug-on-emulator/android-sdk-emulator/

Not long ago the Tester was someone who did his work after the programmers had finished writing their source code, both roles; Programmers and testers were summarized in that. Although the theory was requested for early involvement of the tester in the development cycle, in practice that did not happen. Nowadays, software engineering teams have the challenge of changing that paradigm, and there are at present Agile-based work processes, such as Scrum and eXtreme Programming, that provide an ideal environment for not focusing on their speciality, on the other hand both are developers, but with different responsibilities, that is why the role of the tester can be the best business partner that the client has within the Software Engineering team. The objective of this lecture will be to expose strategies and techniques that take advantage of the full potential of the role of the tester, being this an indispensable functional assembler between the client’s business and the software product.

How do we perform exploratory testing? Do we know real exploratory testing techniques? Is exploratory testing enough to assure quality?

During this presentation you will get you on board the possibilities, sailing on Agile model projects, docking on traditional testing techniques and showing advantages and risks. We will set aside the ad-hoc testing to show why the exploratory testing is being trend in the world.

Success in software development needs the roles of testers, business analysts and developers working together in the team. Together they can assure that the software to be released, fits the business needs and is built within the framework of a quality process. For this, Testing cannot be considered simply as a stage in the process.

Also, to speed up the software delivery (less release time to market) defects should be detected and prevented as soon as possible.
In this conference, we will present techniques and tools that supports this process: such as user stories, conceptual models and automation among others.

Devops is here to stay, coupled with a change in the paradigm of team collaboration. Testing thus becomes a vital part of this new mindset, presenting changes and new challenges for the testing professional. This presentation will cover the basic concepts of Devops and how software testing is integrated into it.

In the last few years, as performance testers we have witnessed a serie of technological changes that led us to incorporate new tools and methodologies in order to meet the client’s needs.

Let’s talk about how we are facing these challenges.

Nowadays, clients come to us with new needs and new requirements. When it comes to the tests, we will focus on how it affects us to work for example with CDNs, serverless approaches, protocols like HTTP2.0, HLS, among others. We want to share based on our experience how we integrate and work with agile methodologies such as Continuous Integration schemes that include performance tests with response times as demanding as faster than 50ms and throughput greater than 1000 tps.

We have developed this knowledge through our work side by side with companies such as Blazemeter, Shutterfly, Disney and Heartflow and while collaborating with the community, for example by developing plugins that support new protocols in JMeter.

These approaches can be implemented in companies like ours or like yours, where large investments or large work teams are not needed. It is just necessary to know all the options the community has to offer.

“… the process of testing the system’s User Interface of the Application Under Test … involves checking the screens with controls such as menus, buttons, icons, and all types of bars… UI is what user sees. “Guru99

Sounds like it would be easy! But what about doing it on 2, 3, or even 5 browsers? What about testing it on multiple devices with different screen sizes? Now it just sounds tedious and repetitive and the more you need to cover increases the likelihood that you will end up missing details on your second and subsequent rounds of testing. Don’t strain your eyes or brain while doing UI Testing; using the right tools you can save time without compromising the quality of your system.

Mocking is a tool used mainly by developers for software creation. It’s use for testing, apart from unit tests; tends to be more limited. Today, the increasing complexity of applications, as well as handling a greater number of automatic tests, makes us use this tool more; to perform our tests.

The aims of this presentation are:

• spread the use and utility, of this tool.
• establish how it can help us, to improve our tests.
• share a real implementation case, which was used to solve specific problems.

Usually automation projects follow a similar pattern, kind of work, duration, size of the team’s, technologies, goals, among others. But, what happens when a project break the rules and its dimension is multiplied on every aspect above mentioned?. We may think that increasing the team size is the way to handle this, but, is that enough?, which are the variables that comes into the board when a project grows?. The main goal of this talk is to, based on real projects experience, give tips and tools to handle this kind of situations, when automation size starts being a challenge and causing problems.

The presentation aims to introduce the Process Model developed in Standard UNIT-ISO/IEC/ IEEE 29119-2. The processes that conform the model and their integration with other technical standards will be presented. It also aims to address the subject of process evaluation and the possibility of declaring conformity to the ISO/IEC/IEEE 29119 series.

One of the biggest problems that a team faces when it comes to automate their first test cases is to know what strategy to implement. In most cases they tend to waste a lot of valuable time in the initial steps of the development, and if they decide to implement a framework in the process surely the following questions will appear:

Is my team ready to implement a framework? What benefits would it bring me? What challenges will we face when developing a test automation framework? Do I really need a framework?

These and many other questions will be answered through examples of good experiences and success cases in this speech.

IoT is the beginning of a revolution in many areas. Most things are going to become “smart” and will start “talking” between each other without human intervention.

Testing must evolve to make this revolution possible. Indeed, the interfaces developed to interact with systems are evolving and the generation of inputs for tests is one of the biggest challenges for testers.

Actually, millions of devices gather data from our environment to analyse it. Political and social decisions are going to be made based on this analysis. This are the first steps that makes us imagine some sci-fi elements in our society.

In this presentation, as well as talking about the challenges we will face testing this new systems, we will introduce you to our experience testing platforms that manages that kind of information.

Structured Programming, Total Quality Management, Agile, Scrum, Devops—and after all this time, projects still stumble and products still drive us crazy. Why? Part of the reason is surely that many projects are flying blind, without sufficient awareness of the status of the product and the problems in it. And why is that? Part of the reason is that the craft of testing is stuck in ideas that we out of date 30 years ago, and are even more out of date today.

Rapid Software Testing (RST) is an approach to software testing developed by James Bach and Michael Bolton. The approach is targeted towards the fastest, least expensive testing that still completely fulfills testing’s mission — to reveal the status of the product through critical thinking, exploration, and experimentation. While process models, artifacts, and tools have roles to play, RST puts the mindset and the skill set of the individual software tester at the center of testing work. Despite the name, Rapid Software Testing isn’t just testing with a speed or sense of urgency; it’s mission-focused testing that eliminates unnecessary work, tells the story of the product, and constantly asks what testing can do to help speed the project as a whole—no matter what the development model might be.

Want to reframe your ways of thinking about the craft? Join Michael for a whirlwind tour through some of the principles and tactics of Rapid Software Testing.