Alexander Todorov

Welcome to FOSDEM 2023. This is our 10th anniversary!

Don't forget to vote in our devroom poll at https://forms.gle/vmwWqjFv5wkVPE2t6!

As a side project the Kiwi TCMS team has started collecting facts about people who've made important contributions to the testing field. We're calling upon other testers for ideas and contributions.

A warm welcome from your devroom managers, practical information, lineup and administrivia. Happy Testing!

A warm welcome from your devroom managers, practical information, lineup and administrivia. Let's make this edition of FOSDEM count!

Happy Testing!

Pylint is the most popular Python source code analyzer which looks for programming errors, helps enforce a coding standard and sniffs for some code smells. It is possible to write plugins to add your own checks, for example enforce all documentation strings to be enclosed with 3 double quotes!

This presentation will focus on how the pylint plugin system works, how to examine AST tree of a piece of code and create a minimalistic plugin from scratch. It will also examine couple of plugins that are used in the Kiwi TCMS project.

In the world of professional QA there are many proprietary test management tools but very few open source ones. This lightning talk will tell the audience why and how we resurrected Kiwi TCMS and what are we doing to make it the best open source test case management system!

FOSDEM marks 10 years since the first version was released and our team will celebrate at the Open Source Test Management stand, Building K, Level 2, stand 10!

Pairwise (a.k.a. all-pairs) testing is a test case generation technique that is based on Microsoft's observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.

I have taken the pairwise approach and applied it during an entire release cycle of Red Hat Enterprise Linux. I've made an experiment where I have reduced the test matrix for 9 product variants and 4 CPU architectures to a size suitable for execution by a single person. In this talk I will explain: - what is the background of the product and how it was traditionally tested - how I've constructed my experiment - how many test cases I was able to remove from the test matrix - how the results and risk level compare to the standard exhaustive test suite!

I will also talk about bugs found and bugs missed by the two approaches.

Mutation testing is a technique in which the software under test is modified in a controlled manner to produce a mutant. Then test cases are executed against each mutant. This helps answer the question "How good is our test suite?". For example if we have made the following change:

- if A and B:
+ if A or B:

and our test suite reports a PASS result that means we are not doing a good job at detecting possible errors.

I have been using mutation testing for production grade software in both Python and Ruby and I'm also the most active contributor to Cosmic Ray, the mutation testing tool for Python. In this talk I will explain how mutation testing works and what it can be used for. I will give practical examples of code which wasn't tested and how to test it and also examples of bugs that I've found. I will also mention some differences between the Python and Ruby tools.