Crash-course: Performance testing

You will learn to identify the weak points of your software and make forecasts of the permissible load on your product. Take with you a set of blanks and tools for testing.
Online
Event is over
Crash-course: Performance testing
Crash-course: Performance testing
Event is over
Event is over
Event is over

Description

Crash Course Performance testing is a two-day intensive dedicated to the theory and practice of performance testing of software products.

On Saturday, September 30, we will look at what types of tests there are, what are the most popular purposes of testing, and how to properly prepare for the process so that the results are valuable and relevant.

On Sunday, October 1, we will move on to practice testing. Let's take a prototype of a multi-component product with a database and a message broker, and on its basis we will understand how to answer business questions: "make it work well", "and how many clients will be able to work". You will also be able to calculate when your product will no longer satisfy the needs of your customers and it is time to rethink it.

Coach — Olexandr Gilevy, Software Engineer Technical Lead at Creatio. 11+ years in IT.

Audience

  • Middle+ level developers
  • QA, QA Lead
  • Participants of the workshop Performance testing who are interested in learning more
  • Those who have experience with similar tests, but want to use them more and better.

Format:

Date and time: September 30, 10:00 - 14:00, (Kyiv time, GMT+3).
October 1, 10:00 - 15:30, (Kyiv time, GMT+3).

Platform: Zoom

Language of the event and presentation: Ukrainian

The number of participants on the second day of the course is limited: 25 places

Program

    September 30, Saturday:
  • Types of tests
  • What is the value of these tests
  • How to choose which type you need
  • Why not all are needed
  • Testing goals
  • How to prepare a quality script. Monolith and microservices.
  • Working with artifacts

    After the intensive, you will be able to:
  1. Help your colleagues improve product quality
  2. Form realistic expectations about development and opportunities.
  3. Act as an organizer of the testing process.
  4. Perform testing without wasting time.
  5. Answer questions from business representatives that they could not formulate correctly.
You will also receive DoR and DoD blanks.

    October 1, Sunday:
  • End to end vs isolated testing
  • Features of monolith testing
  • Testing background services
  • Rest api
  • Consumers of queues
  • Interaction with 3rd party services
  • Test suite preparation and implementation
  • How to draw conclusions

Based on the results of this day, you will be able to implement a test scenario for today's popular backend architectures. learn how to collect metrics and interpret them, identify weak points of software and make forecasts of the permissible load on your product. Take with you a set of blanks and tools for testing.

Agenda

September 30, Saturday

  • 10:00 start, introduction, Test types
  • 11:00 Testing objectives
  • 11:40 Break
  • 12:00 How to prepare a quality script. Monolith and microservices.
  • 13:00 Designing of artifacts
  • 13:30 Presentation of expenditure material
  • 13:35 Q&A

  • October 1, Sunday:

    • 10:00 start, introduction
    • 10:15 Presentation of the test bench and the theoretical part
    • 11:20 Q&A theory
    • 11:40 Break
    • 12:00 Practical work in groups, creation of Test suite
    • 12:30 Presentation of team results
    • 13:00 Implementation of scenarios
    • 13:30 Practical launch of scenarios
    • 14:30 Presentation of team results
    • 15:00 Q&A


    Expert: Oleksandr Gilevy, Software Engineer Technical Lead at Creatio.

    — 11+ years in IT

    — Developer of highly loaded marketing modules

    — Worked with Ciklum, GlobalLogic, Terrasoft

    — Has MIM pre-MBA management & leadership certificates

    Linkedin

    Sign in
    Or by mail
    Sign in
    Or by mail
    Register with email
    Register with email
    Forgot password?