You are here

Sigma

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

Batman Version Control

One of the most alarming things in our industry is that while we immerse ourselves into the world of containers, unikernels, Internet of Things, robotics, machine learning and neural networks, while we strive to be version 2.0 of ourselves, we forget how to master version 0.1 of ourselves. The basics.

This clinic goes back to the roots and taps into one of the key ingredients of software engineering: version control. We'll go through concepts such as release notes, branching models, numbering schemes, release controls, you name it. As such this would be a bit too basic and wouldn't be worth putting into a conference program, which is why we don't use (just) software to learn about version control. Oh no. We use Batman. :)

Once we're done you are able to do version control not only to software systems, but to pretty much anything. The science of it is not limited to zeros and ones. Once we’re done you’ve gone through fantastic and not-so-fantastic storylines, styles, actors, gadgets and of course those horrible nipples in George Clooney's Batsuit that somehow passed unit tests. :D

Key takeaways:

The participants take home key concepts of proper version control. After this clinic they can apply their new or renewed knowledge about version control in their everyday life as software engineers, or they can demand these skills from others while educating them.

Front Line Survival Guide

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.

(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.

 

Subscribe to Sigma