Shift to the right side of your brain - 6th World Congress on Software Qualit...SYSQA BV
Ìý
Mastering one way of testing isn’t enough to be a professional tester nowadays. You need to have knowledge and experience with different ways of testing to test well in every situation. In the presentation Jan Jaap will present different ways of testing like global scripting, session based testing, bug hunts, test tours and pure exploratory testing. All have proven to be useful in agile projects.
In projects where different ways of testing are used drafting a test strategy is different compared to a project where only one way is used. Jan Jaap will explain how a test strategy is made in a project where different ways of testing are used. The things to take into consideration in an agile project will also be explained.
This talk gives you an insight in the different ways of testing you have to master to optimize your test effort.
Main Statement:
Scripted testing is for agile projects too rigid to be used in agile. Testers need to learn different ways of testing to be able to optimize the way of testing in an agile project.
Key Learnings:
Scripted testing, the way of testing most of us learned and used in the past, doesn’t work in agile projects. It’s too rigid
Professional testers need to master different ways of testing to be able to test well in an agile project.
The pros and cons of different ways of testing in agile projects.
TMMi: should you care? Step-Auto Conference 2013, BangaloreSYSQA BV
Ìý
This document discusses the Test Maturity Model integration (TMMi) framework. It begins with an agenda and discusses recent trends in system development and examples where bad testing led to high costs. It then provides an overview of the TMMi, including its five maturity levels for managing test projects and organizations. The benefits of TMMi are listed as improved product quality, test engineering productivity, time and cost savings. Global usage statistics and certification information are presented. Finally, it discusses how physical distance between engineers can impact communication frequency, relating to test process optimization.
Shift to the right side of your brain - 6th World Congress on Software Qualit...SYSQA BV
Ìý
Mastering one way of testing isn’t enough to be a professional tester nowadays. You need to have knowledge and experience with different ways of testing to test well in every situation. In the presentation Jan Jaap will present different ways of testing like global scripting, session based testing, bug hunts, test tours and pure exploratory testing. All have proven to be useful in agile projects.
In projects where different ways of testing are used drafting a test strategy is different compared to a project where only one way is used. Jan Jaap will explain how a test strategy is made in a project where different ways of testing are used. The things to take into consideration in an agile project will also be explained.
This talk gives you an insight in the different ways of testing you have to master to optimize your test effort.
Main Statement:
Scripted testing is for agile projects too rigid to be used in agile. Testers need to learn different ways of testing to be able to optimize the way of testing in an agile project.
Key Learnings:
Scripted testing, the way of testing most of us learned and used in the past, doesn’t work in agile projects. It’s too rigid
Professional testers need to master different ways of testing to be able to test well in an agile project.
The pros and cons of different ways of testing in agile projects.
TMMi: should you care? Step-Auto Conference 2013, BangaloreSYSQA BV
Ìý
This document discusses the Test Maturity Model integration (TMMi) framework. It begins with an agenda and discusses recent trends in system development and examples where bad testing led to high costs. It then provides an overview of the TMMi, including its five maturity levels for managing test projects and organizations. The benefits of TMMi are listed as improved product quality, test engineering productivity, time and cost savings. Global usage statistics and certification information are presented. Finally, it discusses how physical distance between engineers can impact communication frequency, relating to test process optimization.
Experiences with TMMi facts and figures - Romanian Testing Conference 2014SYSQA BV
Ìý
The document discusses experiences with the Test Maturity Model integration (TMMi). It provides an overview of a TMMi assessment that the author conducted for 20 organizations in various industries in the Netherlands. The assessment involved quick scans of five TMMi level 2 process areas: Test Policy and Strategy, Test Planning, Test Monitoring and Control, Test Design and Execution, and Test Environment. The author analyzes the results, finding that organizations scored highest in Test Design and Execution (60%) and lowest in Test Policy and Strategy (30%). The document also discusses why test maturity models like TMMi are relevant for testers globally, including in countries like Romania.
U wilt altijd de best passende testaanpak. Maar kiest u voor de (schijn)zekerheid van scripted testen of gaat u voor flexibiliteit en pragmatiek, waarmee u sneller en efficiënter inzicht krijgt in de kwaliteit van uw systeem?
Op 19 en 20 november organiseerde SYSQA haar jaarlijkse Kennissessies. Dit jaar over Situationeel testen, een antwoord op het genoemde dilemma. Want op ieder project, bij iedere organisatie past een eigen testaanpak.
Tijdens de Kennissessies bleef het niet bij theorie. Na de pauze werd een tweetal aansprekende klantcases toegelicht. Hierbij kwam onder meer aan de orde hoe de betreffende organisaties met Situationeel testen altijd op de meest optimale manier testen, tegen de laagst mogelijke kosten.
De Kennissessies bleken ook dit jaar een middag vol inspiratie, mogelijkheden tot netwerken en kennisuitwisseling en boeiende praktijkcases.
Deelnemers gingen naar huis met nieuwe inzichten waarmee zij op een flexibele en pragmatische wijze sneller en efficiënter inzicht krijgen in de kwaliteit van een systeem!
Combining Requirements Engineering and Testing, QA&TEST Bilbao 2013SYSQA BV
Ìý
Projects that use agile have small, multidisciplinary teams. When every discipline has its own specialist in the team, the team becomes bigger and bigger leading to more communication, coordination and more need for documentation. Combining programming and testing is not a wise decision but combining requirements engineering and testing is very well possible. It even turns out that a lot of communication, documentation and coordination is not necessary. So a lot of time and effort can be saved. During his presentation Jan Jaap tells why testers are excellent requirements engineers (and vice versa) and what the advantages of combining requirements engineering and testing can be. He also addresses what testers should do to get this combined role. With agile becoming more and more popular this can be a possible future for testers.
The idea of combining requirements engineering and testing started with a vision. By now we have enough practical experience to show that is actually works! During the presentation Jan Jaap shares vision and practical experiences.
Scripted testing is too rigid for agile projects. Testers need to learn different test ways to be able to optimize the way of testing in an agile project. To do so you need to become more creative.
Mastering one way of testing isn’t enough to be a professional tester nowadays. You need to have knowledge and experience with different ways of testing to test well in every situation. Especially in agile project a tester needs to master different ways of testing. In this talk Jan Jaap presents different ways of testing and he describes when these are applicable.
Some ways of testing require analytical and logical thinking, others require creative thinking and being able to handle freedom. So with different ways of testing you use different sides of your brain. Most testers are pretty good in logical and analytical thinking, creative thinking is less developed by quite a lot of them. In the second part of the presentation Jan Jaap explains how you can train the right side of your brain and become more creative.
Jan Jaap’s talk gives you insight in the different ways of testing you have to master to optimize your test effort and what you can do to be able to apply the more creative ways of testing.
Use right side of your brain - Agile Testing Days 2014 PotsdamSYSQA BV
Ìý
Scripted testing is too rigid for agile projects. Testers need to learn different test ways to be able to optimize the way of testing in an agile project. To do so you need to become more creative.
Mastering one way of testing isn’t enough to be a professional tester nowadays. You need to have knowledge and experience with different ways of testing to test well in every situation. Especially in agile project a tester needs to master different ways of testing. In this talk Jan Jaap presents different ways of testing and he describes when these are applicable.
Some ways of testing require analytical and logical thinking, others require creative thinking and being able to handle freedom. So with different ways of testing you use different sides of your brain. Most testers are pretty good in logical and analytical thinking, creative thinking is less developed by quite a lot of them. In the second part of the presentation Jan Jaap explains how you can train the right side of your brain and become more creative.
Jan Jaap’s talk gives you insight in the different ways of testing you have to master to optimize your test effort and what you can do to be able to apply the more creative ways of testing.
(source: agiletestingdays.com)
This document lists several early human species: Australopithecus, Homo habilis, Homo erectus, Homo neanderthalensis, and Homo de Cromenyó. It provides a brief timeline of hominin evolution starting with Australopithecus and progressing through Homo species that include Homo habilis, Homo erectus, Homo neanderthalensis, and ending with Homo de Cromenyó.
Jaume vino a la clase de tercer grado para tocar el violÃn. Explicó que el violÃn es un instrumento italiano con cuatro cuerdas, Mi, Sol, Fa y La, y que se toca con el arco cubierto con pelos de caballo. Jaume tocó una canción para la clase y les enseñó que el violÃn tenÃa un puente que sostenÃa las cuerdas, y que ese violÃn en particular tenÃa 100 años.
2. l
• La prehistòria va començar l’any 7 milions a.c.
• I va acabar l’any 400.000 a.c.
• La prehistòria es divideix en dues etapes:
• L’edat de pedra i l’edat dels metalls.