Software Testing & Automation Masterclass

Ministry of Testing Athens (MOTA) is a highly active network of scientists and IT professionals specializing in Software Testing. JavaScript and React Masterclass, as well as Software Testing and Automation Masterclass instructors are active members and member of the organizing committee of MoT Athens with extensive experience in software development projects & software testing projects.

Special fees apply for MOTA members. Calls us at 210-3680911 for more information.

The seminar is designed for software developers, quality assurance engineers, web developers, IT Project Managers as well as to students or graduates of IT schools who wish to upgrade their knowledge in Software Testing and automation.

Prerequisites: recommended to have basic programming knowledge in at least one language such as Python, Java or JavaScript, as it will be necessary for writing and executing automation scripts. Familiarity with software development concepts. Basic understanding of web and mobile applications. 

• Familiarize with Testing Theory and Terms.

• Being able to to identify common terminologies such as regression testing, black box testing ,smoke testing , test cases etc

• Being able to present an overview of automation testing techniques and best practises specific to mobile and web applications (e.g Appium)

• Apply Test Design Techniques such as Page Object Model and explain the concept of these techniques and their significance in building scalable test automation frameworks as this is widely used as design pattern for organizing test code

• Being able of designing and setting up a test automation framework from scratch using WebDriverIO or Playwright and cover key components of a test automation suite, including test environment setup, project structure, configuration management, and dependency management.

• Being able to Provide a Complete Reporting Approach, introduce tools for generating detailed test reports and metrics

• Being able to Identify and Propose Parallel Test Execution under a CI/CD Model, explain the concept of parallel test execution and its benefits in accelerating test cycles and reducing time-to-feedback and provide guidelines for configuring and optimising parallel test execution setups to maximize efficiency and resource utilization

Watch the video from our recent Software Testing event!

Learn more about the latest trends, skills, and career opportunities in Software Testing through insightful presentations and a round table discussion held on October 8th, featuring top industry professionals and instructors of our software testing seminars.

Software Testing Fundamentals

• What is Software Testing
• Testing Objectives
• Testing Principles
• Software Development Life Cycle
• Software Testing Life Cycle
• Software development models (Agile, Waterfall, V-model)
• Requirement Analysis
• Test Planning
• Test Case Development
• Test environment setup
• Test Execution
• Requirement Traceability Matrix (RTM)
• Black Box Testing

Manual Testing

• How to perform manual Testing
• The role of QA in Agile
• Goals of manual Testing
• What is business/Software Requirement
• What is a user story
• What is acceptance criteria
• What is a test case
• Test scenario vs Test case
• How to write a test case
• Best practises for writing good test case

Exercises : For a given Web page or a feature create several acceptance criteria along with several test cases. Create a traceability matrix based on the acceptance criteria and the test cases created.

Feedback & Open discussion on how the test cases where created, possible findings, thing to improve regarding the tc design

Bug vs Defect

• Bug Report
• Severity vs Priority with examples
• Defect/Bug Life Cycle
• What is a test suite
• Regression Testing
• Smoke Testing
• Manual vs Automation
• Software Testing Techniques
• Boundary Value Analysis
• Equivalence Class partitioning
• Decision Table Based Testing
• State Transition
• Error guessing
• Functional Testing
• Usability Testing
• Compatibility Testing
• Performance Testing
• Security Testing
• Crowd Testing

Exercises : For a given Web page or a feature create several test cases and organise them on test suites, like regression suite, smoke suite, security suite etc

Analyze exercises & Open discussion on how the test cases where organised, how each test suite was created and if a test case could be used in more than one suite.

Web Applications Simple Architecture

• What is Web Testing
• What is Automation Testing
• Why Automation Testing
• Which Test cases to automate
• Which type of tests should be automated ?
• Flakiness and how to eliminate it
• Test Pyramid

Unit Testing

• Functional Testing
• Visual Testing
• End-to-end Testing
• What is Webdriver
• What is Webdriver protocol
• Automation Frameworks
• Selecting an Automation framework
• Locator strategies
• Why Mocha
• Multiple question test as homework with everything that was discussed from previous days

Analyse, discuss test results per user

• Mobile App Types
• Developing Tools
• Mobile Application Testing
• Why Mobile Automation
• Mobile Test Pyramid
• Desktop browsers

Mobile Simulators/Emulators

• Real Devices
• What is Appium and why use Appium
• Appium Philosophy and Appium Design
• Appium concepts
• Desired capabilities
• Session
• Appium Server
• How to install Appium
• Desired capabilities examples

Multiple question test as homework with everything that was discussed from previous days
Analyze, discuss test results per user.

Test Driven Development

• Behaviour Driven Development
• Anatomy of a Mocha Test suite
• Spec Files
• Describe blocks
• It Statement
• Expectations
• Disable suites
• Disable Tests

What is WebdriverIO

• WebdriverIO Characteristics
• WebdriverIO setup
• WebdriverIO modes
• Sync VS Async mode
• Services in WebdriverIO
• Capabilities
• Elements Selectors
• Browser object
• WebdriverIO Protocol
• Element object
• Page Object model Description
• Assestion Library (expect)
• Assertion Library – main methods

Multiple question test as homework with everything that was discussed from previous days

Analyse, discuss test results per user

First Test

• How to run a spec file
• How to run a test suite
• Constants
• Reporter - install packages
• Reporter Configuration
• Unhappy login scenarios

Add some extra test cases

• Validate that all products are present
• Validate that the details of a product can be opened
• Validate that a product can be added into the cart
• Validate that the products can be removed from the cart

Exercise: For a given Web page create extra test cases containing: Open the burger menu | Open the about page | Be able to logout
Analyze exercises & Open discussion on how the test cases where created, possible findings, thing to improve regarding the tc design. Ways to debug a failed test. Visual regression testing.

Describe a project’s structure in general

• Create an Android Emulator
• Install the apk into an Android Emulator
• Appium Desktop
• Configure Appium Capabilities
• Navigate inside an App and check Accessibility ID
• Login spec file

Create Constants

• Create Test scenarios for Login
• Swipe action
• Android Debug bridge
• Add FingerPrint on Android Emulator
• Create our first Touch/Face ID Test. Login Authentication with Touch ID

CI/CD Model description. What it is. What does it offer

• Pipelines
• Saucelabs Integration

Exercise: For a given Web page create extra test cases for geolocation. Provide the adb commands and try to create the respective scenarios: Allow App to access device’s location | Do not allow app to access device’s location

Analyze exercises & Open discussion on how the test cases where created, possible findings, thing to improve regarding the tc design.Ways to debug a failed test.

Introduction to Playwright

• Explore Playwright
• Install Playwright
• Introduction to a Playwright project

Understanding the Playwright config file

• Writing Tests
• Running Tests
• Advanced Features
• Core aspects of a Playwright Test
• Locator Strategies

How to organise your tests using the POM approach

• Organise your tests with beforeAll or beforeEach
• Create our first login test

Exercise: For a given Web page create extra test cases containing some unhappy path login test cases

• Analyze exercises & Open discussion on how the test cases where created, possible findings, thing to improve regarding the TC design.
• Ways to debug a failed test
• Create some extra test cases like 
• Validate that all products are present

Extra test cases creation:

• Validate that all products are present
• Validate that the products can be removed from the cart
• Validate that the details of a product can be opened
• Be able to logout

Exercise: For a given Web page create extra test cases containing: Open the burger menu | Open the about page | Be able to logout
Analyze exercises from the previous week. Open discussion on how the test cases where created, possible findings, thing to improve regarding the TC design. Improve your tests using the afterAll /afterEach 

Playwright hints
Q&A session and Closure - Lessons learned - Action Plan - next steps