Мартыненко Сергей
Преподаватель - нет
Moscow, Russia

Первую программу написал в 1986. Выполнял роли: программиста, эникейщика, тестировщика, проектировщика интерфейсов, руководителя проектов и т.д.

Продолжаю писать "Байки для оруженосца".

Talks (5)
  • 22.06.2021
    A calculator for the effective Owl manager

    I like the scientific method of knowing the world.

    1. We put forward a hypothesis. We make it verifiable (scientific).
    2. We conduct an experiment.
    3. We accept the results of the experiment.

    Sometimes my colleagues and I do experiments. Some of the results amazed even me. For example, testers solve problems for analysis better than analysts. In my talk, I will tell you the results of an experiment in creating software for bad requirements. And I'll try to show you how to make them good.

    • Easy
    • 40 min
    • Analyst Days / 13
  • 20.03.2020
    Key Testing Metrics

    Before the talk, I highly recommend reading Goldratt’s books "Haystack Syndrome" and "Goal-1". The material is complex without a preliminary study of the base. On a three-point scale of complexity, this material is about five.

    For seed, I’ll give a list of metrics that can be measured in principle. As the talk will show, this is the road to nowhere.

    1. A number of bugs found. 

    - In general 

    - By time 

    - Per-user 

    - Only critical for the software functionality 

    2. The number of reports from the customer/client.

    3. Time spent on testing of the next delivery.

    4. The number of tests that were successful or not successful.

    5. Percentage of code coverage (“What can I get from tracking this indicator?”).

    6. Percentage of test coverage of requirements. 

    7. The number of software failures over a period of time.

    8. The number of elements that the tester clicked (covered by manual testing). 

    9. The number of re-opened tasks for testing. 

    This list is more informational noise than information.

    • Hard
    • 40 min
    • SQA Days / 27
  • 06.01.2017
    Будет после принятия

    Pile of books on software development contains information that the requirements must be tested. And, according to statistics, more errors build into a product on the levels of creation and design of the requirements, than during the coding.

    As soon as it comes to practice, very often the requirements just do not pass the proofread procedure (and sometimes do not read them). If it comes to a proofreading, it usually ends up by spelling and punctuation. And then 
    the error gets to the end user.

    Why? Many reasons are for this. The first - the psychology. Here "isn't thought up here" and different contexts of thought, and much more. The second - lack of the described verification techniques. There are a lot of literatures and courses, but there is no practically on the verification subject.

    The topic will be considered at the workshop:
    * Psychological barriers to verification;
    * Verification techniques;
    * E
    xample of an use-case verification submitted by the participants of the uml2.ru community.

    • Average
    • 1h 30 min
    • Analyst Days / 6
  • 09.10.2015
    Preparation of the test strategy for high-risked and profitable project.

    Business scenario to be considered: 

    1. Innovative project.
    2. More than half of these projects failed. 
    3. Success projects are bring millions a week. Not in rubles. Every extra week of development is a multi-million losses. Priority - speed.
    4. The error in the system, similar to that described in Russian here (http://goo.gl/xJfVcj), can make the company bankrupt in an hour.

    In my report you will:

    • See the generalized algorithm for constructing a testing strategy.
    • See a look how to built the facet by facet of the strategy and how to improve the flow in concrete case.
    • See the difference between strategy and non-strategy.

    Expected Audience:

    • Test Managers: they have to write and defend the testing strategy.
    • Project managers: they have to coordinate the testing strategy with the general strategy of the development.
    • Engeenirs: they have to understand and adopt the strategy. 

    Level of this report is very high. 
    Knowledge of works by Deming and Goldratt is preferable.

    • Hard
    • 40 min
    • SQA Days / 18
  • 11.01.2014
    Testing strategies. 42 ways to make your project successful

    STRATEGY (in operations research) - a method of using tools and resources aimed to achieve the goals of the operation. The strategy defines by accepted determined values of ​​controlled variables. For selection of these values ​​is important to know the conditions of "external environment", i.e. the values ​​of uncontrolled variables. In multistep processes the method can change itself, in this case the strategy defines the rules for further action (ie, the choice of the trajectory) based on the obtained information about each stage of the process and changes in the environment. The task of operations research, as a rule, is precisely in selecting the optimal number of alternative strategies (alternatives) based on one or another criterion. From scientific, proceed to the common understanding. Strategy is prioritization kinds of action aimed at achieving results with the lowest cost. For example, an attack of fortified enemy positions during World War II could suggest the following steps: pre-clearance, barrage, a joint attack by infantry and tanks. Use the same steps in the reverse sequence will lead to increased losses at the achievement of the desired result. The same way, choosing the right testing strategy can increase testing efficiency significantly. The opposite is also true. I witnessed how a wrong testing strategy led to a decrease in efficiency tenfold. I started to collect and classify the material in 2001. Almost all of the strategies that I will speak, I used in my projects, or watched their live application. As well I analyzed the limits of their applicability. As far as I know, there is no such classification like this in the ex-Soviet Union.

    • Average
    • 40 min
    • SQA Days / 15
To leave a feedback you need to

Chat with us, we are online!