To wersja testowa nowego serwisu infoShare Academy — wyświetlane treści i oferta nie są wiążące ani kompletne

Testing

Robot Framework

Robot Framework allows teams to introduce automated tests that are understandable not only for technical staff.

Duration
2h
Ask about the program → See all
Who it's for

Ideal for teams that…

1 IT staff with minimal programming knowledge (e.g., juniors, manual testers). No prior Python knowledge is required.
2 QA engineers who want to use tools that improve communication with the business side.
3 Manual testers who want to develop their skills and introduce automated testing in their company.
4 Developers responsible for testing their own software.
5 Automation testers who want to learn a new framework increasingly used in quality assurance.
Outcomes after the program

Software testing and quality — automation and QA methodologies.

✓

Practical and proven applications of Robot Framework

✓

How to convert manual test cases into automated ones

✓

How to quickly start writing automated tests without building complex architecture

✓

How to read reports to quickly and effectively detect software errors

✓

How to extend Robot Framework with custom keywords for specific modules

✓

How to write clean and readable code

Program

What we actually do

  • · Module 1: Introduction Demo – running simple tests and showing reports Training plan (timeframe, agenda, breaks, other organizational matters) Introduction round (participants’ roles and motivations) Training objectives (example of RF in action)
  • · Module 2: Testing Basics What testing is and its goals Manual vs automated tests What automation is and its objectives
  • · Module 3: Preparation for Automation Exploring and understanding the system Identifying areas for automation Introduction to Robot Framework Preparing test cases
  • · Module 4: Introduction to Robot Framework Why it’s so powerful (libraries, built-in keywords, types of tests) Installation, version check, execution File sections Settings Variables Test Cases Tasks Keywords Comments Supported file types Case sensitivity and underscores
  • · Module 5: First Automated Test Case Dry test case using built-in keywords RF output files (output.xml, log.html, report.html, xunit.xml) Reading and understanding test reports Creating a failing test and analyzing results
  • · Module 6: Variables Introduction to variables, syntax Scalar $, List @, Dictionary &, Numbers Built-in variables Variable tables and files Command line variables
  • · Module 7: Libraries Using keywords from built-in libraries Loading third-party libraries
  • · Module 8: Writing Custom Keywords Keyword Driven Testing (KDT) approach Creating keywords – name, arguments, return values Returning different types from keywords Python equivalents
  • · Module 9: Advanced Keywords Arguments (default, named, embedded in keyword) Exercises creating custom keywords
  • · Module 10: Code Execution Control FOR loops Conditional execution (Run Keyword If, Set Variable If)
  • · Module 11: Organizing Tests and Execution Control Combining tests into suites File organization and section order
  • · Module 12: Command Line Options Tagging – include and exclude Other options
  • · Module 13: Logging and Reading Output
  • · Module 14: Setup and Teardown Preparing and cleaning up data Suite-level and test-level setup/teardown
  • · Module 15: Global Variables, Suites, and Tests
  • · Module 16: Additional Topics Documenting code Resource files Data Driven Testing (DDT) Behavior Driven Development (BDD) with Gherkin
  • · Module 17: GUI Testing with Selenium Library
  • · Module 18: Coding Guidelines
  • · Module 19: Advanced Topics YAML files Test parallelization (pabot) Creating libraries
  • · Module 20: Closing Certificates Feedback survey
Every module is adapted to your stack and context. The above is a starting point — not a fixed agenda.
How we work

From brief to retro in 30 days.

01

Brief & diagnosis

A call with the team lead + a short survey for participants. We define goals, gap and context.

02

Program customization

We adapt modules, case studies and code examples to your stack. Approval in 5 days.

03

Workshop

Trainer-led sessions, hands-on, code review. Mentor available between sessions too.

04

Retro + report

Outcome report for the team and lead. 30 days of consulting included.

Inquiry

Send a brief. We'll reply within 1 day.

After a short brief we'll prepare a program and a quote. No obligations — it's just a starting point.

✓Quote within 48h of the brief
✓First session within 30 days
✓Pilot before the full decision
✓VAT invoice, payment in instalments possible

How we handle your data

We process your business data (name, work e-mail, phone number, company, job title) in order to handle your corporate training inquiry and prepare an offer. The data controller is infoShare Academy Sp. z o.o., Al. Grunwaldzka 472B, 80-309 Gdańsk. Providing the data is voluntary but necessary to receive a response. You have the right to access, rectify, erase or restrict the processing of your data and to object to it. Full information is available in our data processing notice.

Optional marketing consents

The controller of your personal data is infoShare Academy sp. z o.o. The rules for processing personal data are set out in the Privacy Policy and the Data Processing Notice.

Other programs for teams

See all →
Testing

BDD

Software testing and quality — automation and QA methodologies.

16h · 2 days →
Testing

Frontend testing

Software testing and quality — automation and QA methodologies.

21h · 3 days →
Testing

Java Testing - Basics

Software testing and quality — automation and QA methodologies.

16h · 2 days →