You are here


PARTNER TRACK: Automated Non-Functional Testing and Quantitative Estimation

Please note that this is a sponsored track.

There are some common questions which bother QA and Scrum teams: How to do automated non-functional testing In development Stabilization phase? Can we control the failure rate if there are quantitative requires?

During the presentation, I would like to share our experience to run automated non-functional testing and quantitative estimation.

Key takeaways:

  • How to do automated non-functional testing In development Stabilization phase.
  • How to do quantitative estimation based on automated non-functional testing results.

End to End Tests with Protractor

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

Most people will have heard that Protractor is an end-to-end test framework for AngularJS applications. But how does it differ when trying to test against Angular applications? How does using TypeScript change how our page objects should look? How should I setup the project? And where do promises fit into all this?

Join this workshop if you’ve been trying to navigate this landscape and learn how to get up to speed with writing tests with Protractor for Angular applications. The workshop will also cover how to write tests that are expressive, and provide guidance on how to keep them maintainable for the future.

Key takeaways:

  • Project setup for end to end tests with Protractor
  • How to create page objects in TypeScript to make a DSL
  • How to deal with promises
  • Other patterns and ideas for making your tests maintainable for the future

Prerequisites for the workshop

Red Teaming on Production


We are all familiar with the notion of penetration testing, where security experts will try to find all of the vulnerabilities present within a small surface area, such as a public facing web application. This narrow-scope approach to security testing is of course necessary. But real hackers often do not care to attack such hardened targets, and will instead leverage social engineering and other techniques, which are harder to defend against and can yield a greater payoff.

Introducing Red Teaming

Red Teaming is real adversary simulation, where the “hired guns” will try to get to your crown jewels by almost any means necessary, including social engineering and physical intrusions. A Red Team does not attempt to find every vulnerability that you have, but rather “the path of least resistance” to your company’s most treasured assets. In summary, Red Teaming is the experience of “really getting hacked”, but without the inflicted damage.

The key question that needs answering is how does one execute Red Teaming on a production environment safely.  Come and hear “Tales from the Trenches: Red Teaming on production” to find the answer.

Key Takeaways

When we are done you will understand what it means to do Red Teaming on a production environment, what are the advantages over classical penetration testing, and what red teaming can not replace. Most importantly, you will understand why this is the future!

Front Line Survival Guide

Note: There are prerequisites for attending this workshop. Please see the prerequisites section.

Performance Testing is an important part in today’s test missions. Putting load onto a system until it crashes is nothing new. But in practice, load or stress tests often go short because of time or budget constraints.

Gatling is a new tool to address this shortcoming allowing to efficiently write and maintain performance tests and include their execution into CI/CD pipelines.

In this workshop you will learn the foundations of performance testing, how to create and execute user scenarios and load models with Gatling's DSL. To juice up theoretical basics, you'll be faced with challenging practical exercises.

Key Takeaways:

Participants will learn how to: create performance scripts, define user scenarios load models and learn how to use the Gatling Load Testing framework efficiently.


Please see the guide from here:

(Re)Invent Your Test Strategy

Testing is a craft, but it is also and for many foremost a job. A job you do day in day out, evolving with all the rituals every employee develops over time. These rituals, together with all sorts of other external factors (deadlines, pressure, etc.) often means that we don’t have a formalised test strategy or that we are no longer reconsidering the strategies we set out from the start. Having the right strategy in testing is important to stay as efficient and effective as you can be. One of the hardest things you can ask a Tester is: "What is your current Testing Strategy?".

This workshop wants to reignite your strategic fire by placing you in small groups with your fellow testers. Together you will devise a strategy for a real life product which includes methods, tools and planning. However, just like in reality the context will change, and our strategy must change accordingly to aptly react to that change. The workshop will use the TestSphere cards as a support to spark discussions and for bolstering your strategy.

Key takeaways:

  1. You will work as a team to discuss and describe a strategy to tackle a real life case and problem.
  2. You will work out a proposal to convince your manager which can involve tools, methods and planning.
  3. You will use TestSphere as a tool to uncover unknown-unknowns and strengthen your strategy.


Starting With Performance (and Reliability) Testing

Sold out

Who wants to learn more about Performance Testing?

Perhaps you’ve been nominteered to establish a performance testing practice. Maybe you’ve experienced a performance problem and want to address this risk in the future. It could even be that you are ready to take your career ahead another step. However you’ve arrived here, let’s get you started on this journey with an understanding of a typical performance testing project methodology.

We will have some lecture, and some hands-on. You will run a live load test, and interpret the results.

Tutorial outline:

  • Goals of Performance Testing: Reducing Risk, Scaling, Capacity Planning, and Providing Development Feedback
  • Roles of the Performance Tester
  • Designing Tests: Doing the best test(s) you have time, tools, facilities, and people to do
  • Scripting Tests: Test scripting details, Data Models
  • Modeling Workloads: Understanding Application and Session Flow
  • Problems in realism: Understanding transactions, workload concurrency and peaks
  • Scenarios (Simulation, Breakpoint/Stress, Benchmark, Soak, Exploratory)
  • Test Environments and Scaling Results
  • Monitoring and Instrumenting: granularity, understanding hard and soft resources
  • Running Tests and Validating results
  • Front-End Analysis
  • Interpreting results and Reporting


Key takeaways:

  • Understanding the phases of a performance testing project
  • Knowing a bit about each of the phases of a typical performance testing project
  • Having a framework for further education and self-study
  • Run a performance test
Subscribe to Sigma