In 7 noiembrie 2019, plina de emotie si cu planurile foarte bine structurate in minte, am ajuns la “Tabara de Toamna” de la Albota.
Stiam ca scopul meu cel mai mare (in afara de a invata, a socializa cu persoane din domeniu) era ca in viitorul apropiat sa pun Brasovul pe harta “Tabara de Testare”. Ma framanta ideea ca un oras cu o comunitate IT destul de importanta nu este deja parte a acestui grup fain.
Asa ca am inceput sa vorbesc, sa intreb, sa aflu cum fac altii lucrurile sa mearga, intalnirile sa se desfasoare, speakerii sa fie dornici de a prezenta si in final comunitatea sa se adune luna de luna.
3 luni mai tarziu, in 27 februarie 2020 toate planurile si
ideile au prins viata la “Tabara de Testare Brasov – Kick off meeting”.
Emotii, colegi de la Bucuresti alaturi, o sala faina gata sa ne gazduiasca, suport si incurajari via Slack de la prietenii “Tabara de Testare” din alte orase, prajituri si multe zambete, persoane gata sa sustina ideea si lume noua curioasa sa afle care e planul pentru viitor, o prezentare captivanta sustinuta de Andrei Pirvulescu, multe poze si un joc moderat de Andrei Dobrin, care a cerut munca in echipa si comunicare. Acestea au fost ideile care au caracterizat kick off meeting-ul.
In mai putin de 30 de zile va avea loc cea de-a doua intalnire.
On the 29th of January we had a meetup on experiential learning. We had fun with the 8bit game of our childhood, Pacman, while the workshop facilitators guided the learning on bug investigation: Andreea Vescan, professor on Testing at Babes Bolyai University, and Adina Moldovan, software tester and consultant at Altom.
We went through the four steps David A. Kolb suggests. We started by experiencing the game, and its’ bugs. After, we reflected on our experience: from actions to how we felt, a step that we rarely do naturally in our day to day life. Then we analyzed more deeply how we worked, trying to figure out why we did what we did, followed by conceptualizing a group model on bug investigation. Sixteen people (in the picture, and more behind the scenes): testers, professors, students, offered seven versions for our goal: if we were to teach bug investigation in seven steps, which would they be? Together, we went though each proposal and came out with a group version.
The process was engaging, and it’s interesting to reflect on the results:
how people can use different words but mean the same thing
how much hands on experience can drive the creation of useful models
how anyone can do it, or
how easily we can build relevant models though the power of the group.
This part of idea development (abstractization & conceptualization), in our case modeling seven steps to bug investigation, was challenging but facilitated a deeper understanding on the subject. In the mindmap below, the words in bigger font are the seven steps we chose as a group, and the words deriving from them are all the different versions and aspects the people proposed before the categories existed.
We encourage you all to try an experiential learning experience with any goal. To make the process smoother in a group, we used menti.com to submit each version (see heatmap), and the consecrated flip-chart to group the terms together while discussing them. If you have the possibility to use directly a mind-mapping tool, we think it’s a great alternative over the flipchart. We mind-mapped it after the meetup.
Our meetup ended with sharing ideas about where we’ll use what we learned. This is an important aspect to challenge our mind to think at, so when the opportunity comes we’ll know what to do.
We hope you enjoyed our sharing and when you try, let us know how your experiential learning went. TdT Cluj team.
Mai avem locuri disponibile la workshop-urile de Sambata.
Grab them while you can!!!
La “Cum sa pescuiesti mai repede si mai eficient”, Böjte Tamás va povesti despre caracteristicile Java8 ce sunt foarte utile in testarea automata. Acest workshop este ideal pentru orice Test engineer care doreste sa isi aprofundeze cunostintele de Java. O sa scriem impreuna un cod mai ordonat, dar o sa trecem si prin notiuni de baza pentru colegii la inceput de drum.
La “La pescuit de soft skills si distractie.”, Andrei Dobrin va facilita trei activitati care au ca scop principal distractia, comunicarea si cooperarea. Doua exercitii au fost facute de Dan Ashby in cadrul RTC2019, iar al 3lea este jocul activity in care participantii or sa mimeze sau or sa deseneze termeni pe care ii folosim zi de zi in QA. Tu cum ai mima performance testing sau cum ai desena Jenkins? Acest workshop este ideal pentru oricine doreste sa invete mai multe despre active listening, comunicare, cooperare intr-un mediu fun.
Intr-o editie anterioara a TDT Bucuresti, Stefan a mimat cu succes Load testing!
Aici gasesti toate atelierele pregatite pentru Tabara de Testare 2019, iar aici gasesti formularul de inscriere.
Te asteptam cu drag intr-o adevarata atmosfera de tabara, unde o sa ai ocazia sa discuti si sa faci schimb de idei cu alti 60+ colegi din testare, cu siguranta in fiecare zi discutiile vor continua la un pahar de vin fiert sau o bere rece.
Am definitivat agenda Taberei din acest an si am deschis inscrierile. Te invitam sa vizualizezi atelierele pe care content owner-ii din acest an le-au propus si sa te inscrii la cele care sunt de interes pentru tine folosind formularul de inscriere!
Daca nu ai participat la editiile anterioare, sa stii ca e un eveniment in care ne adum impreuna cu alti testeri, maxim 80 la numar, si participam la ateliere practice. Adica lucram 2 zile la imbunatatirea unor abilitati utile in activitatea noastra. Avem ocazia sa ii cunoastem pe ceilalti testeri si sa impartasim provocarile, interesele si motivatia noastra.
As CodeCamp 2018 is drawing near, I keep perusing my notes and wondering about the upcoming talks. Becoming CodeCamper for a day was such a rewarding experience last year, especially since it gave me a sense of belonging and allowed me to get together with fellow enthusiasts. #ByTheCommunityForTheCommunity is the shared vision that prompted the Testing Camp and the CodeCamp to partner up in the first place. Since April 2016 (Iasi) and May 2016 (Cluj), this partnership has brought together Content Owners as well as Participants from various IT fields, some of which have later on delivered presentations or workshops at the Testing Camp Meetups.
I’ve been switching between the Tester and Developer hats for a while now, which is all the more reason to look forward to the next gathering, with its cross-disciplinary approach. But for now, I’d like to give you an overview of what I took from the previous edition.
When I registered for the 2017 edition of CodeCamp in Timisoara (our first one), I struggled with a different kind of “knapsack problem”. Choosing between 8 parallel tracks and more than 50 speakers was no easy endeavor. Packing them in one day either. Especially since the Testing Camp had been allotted an entire track on the agenda. However, once I had settled on my conference line-up, I simply couldn’t wait to get there and learn the ropes of new testing, marketing and development-related topics.
Just read on for snippets from my Camping Log.
Why do Projects Fail?
I first pitched camp at Track 5 and
attended a presentation delivered by Andreea Bozesan and Andrei Panu
from Softvision. It focused on reasons why projects may start off on the
wrong foot or simply face hurdles along the way, which prevent them
from achieving their milestones or trigger failure altogether. I found
the speakers’ approach highly useful, because it provided examples for
all stages of the Product Life Cycle. Instead of mere theoretical scenarios, these examples illustrated actual challenges from real-life projects, such as:
skipping the feasibility study
budgeting little time for software architecture and QA
scope creep
poor managing of remote teams and/or cultural differences
insufficient project tracking
(to name but a few of the situations brought to the table).
If I were to find some common ground
between all these examples, I’d say that, more often than not, it all
boils down to (lack of) communication. Among the takeaways suggested for preventing project failure, I jotted down the following:
management and stakeholder support
clear vision & realistic objectives
clear and optimized scope
formal methodology in place
skilled and motivated team
proper testing process
user involvement
Using Technology in Online Marketing: Chatbots
The second presentation targeted (but was not limited to) the Generation Z
and the marketing strategies that can be employed to engage such users,
which are basically born with a digital footprint and favor social
media interactions. Georgiana Dragomir from Grapefruit gave us a taster
of how Chatbots foster customer loyalty and retention. Several case
studies backed this statement up and provided memorable examples. Here
are some of them:
The Pizza Hut chatbot
(Sales & Advertising) – available via Facebook Messenger and
Twitter. It is meant to simplify the ordering experience and catch up
with Domino’s more advanced technical options. After a mere three
months, Pizza Hut managed to increase its engagement and boost customer
retention.
SIMI (Creative
Marketing) – designed as a Personal Bartender Chatbot, which comes up
with recipes based on the ingredients input by the users. To prompt
retention, it also rewards its customers with free drinks and paid taxi
rides to and from the bar, so as to avoid any drunk driving.
ERICA (Customer
Service) – the digital assistant, released by the Bank of America. It is
a proactive chatbot, which uses AI, predictive analytics and cognitive
messages to oversee payments and offer support in developing saving
plans. This initiative is aimed at encouraging customers to change their
spending habits.
Consequently, emphasis was placed on the
marketing aspects, rather than on the technical implementation. This
shift in perspective provided me with valuable interdisciplinary
insights. What I also found interesting in addition to the use cases, is
the fact that Facebook Messenger offers the necessary infrastructure
for developing chatbots. This means that it takes little time to
implement and maintain one, thus making it more accessible to developers
and the end users alike.
Infrastructure Testing for Docker Containers
Next on my line-up was the presentation
delivered by Alina Ionescu from Haufe Group. It brought me closer to a
type of testing, which I was yet unfamiliar with. Consequently, I found
it very useful that Alina focused on an actual project to contextualize
the subject matter. Infrastructure Testing had been conducted for a
large backend project with more than 10 other dependencies. This sheer
scale entails working with an immutable infrastructure. Since some
Docker containers don’t complete at the same time, the need arises to
check that everything is up and running.
Apart from the technical benefits of using such tools as Bash or Docker,
what I found particularly interesting was the process itself, which is
aimed at ensuring transparency and communication at team level. The workflow
involves creating a ticket before the actual deploy, so that all
involved parties are informed. The infrastructure tests are run. If they
pass, the ticket is closed automatically and everyone is again briefed.
In case of test failure, it is possible to roll back and work on a
solution. Prioritizing your tests is also an option.
Having pointed out the process, it is
also well worth mentioning that Infrastructure Testing is only one of
the stages, slotted after the code deploy. Below is a visual rendition
of how testing is parceled out:
(Adapted from Alina’s presentation)
Visualizing the process aided me in understanding each stage better and grasping the benefits of this “Deploy-Destroy-Redeploy”
approach, which is less time-consuming and more performance-oriented.
Writing automated tests in the same environment that the Developers use
is another plus. The deployments thus become more efficient and
predictable, while focus is placed on decreased recovery times and
higher quality. An extensive project like the one in the example
benefits from this approach, which I think can also come in handy when
scaling an initially smaller project.
A Game of Performance
Delivered by Alex Moldovan from Fortech,
this presentation revolved around the mobile aspect of performance,
suggesting various approaches to handling browser issues, app size and JavaScript.
It was quite intriguing for me to take a
peek behind the curtains, especially since I had already come across
and muddled through some of those issues myself, yet only as a user.
Being introduced to the challenges mobile developers face on the
eclectic and ever-evolving browser and device market really puts things
into perspective. For one, it definitely makes you empathize more with
the struggles put into providing users with an efficient, effective,
satisfactory and accessible experience.
The catchy titles, the well-chosen visuals and the Alice-Developer-Persona made the suggested solutions more memorable.
Here are some of my takeaways:
Testing Trends or Buzzwords?
The last item on the agenda of the
Testing Camp set about rounding off a diverse and engaging Track.
Throughout their sessions, the content owners had offered their view on a
number of topics, ranging from Infrastructure, Front-end, Continuous
Delivery to Planning, as well as Exploratory Testing. Therefore, it
seemed only fitting for Iulian Benea from Steadforce to prompt the
audience to consider how Testing is evolving. Three aspects provided me
with ample food for thought.
First of all, Iulian addressed the current need to automate tests
as much as possible, in order to catch as many bugs as possible at an
early stage. While this approach is cost-effective and less
time-consuming, I think it should still leave room for Exploratory
Testing, which can uncover important bugs in a shorter time span and can
also be conducted in a structured and traceable manner (e.g. through SBTM).
The second aspect revolved around the specialization of testing. Usability,
Performance, Security, Data Analysis and DevOps are just some of the
focus points, which have gained leverage and popularity over time. These
are more often than not connected with or influenced by the new fields,
that are high in demand nowadays and constitute the third course of our
“food for thought” meal: Big Data, Augmented Reality, Artificial
Intelligence, Internet of Things and the coveted Blockchain Technology,
to name but a few.
Drawing on these three aspects, we went
on to discuss how Testers could adapt to such almost paradigmatic
changes, in order to perform their tasks. Developing one’s skills beyond
testing has become paramount. Adding request analysis, scripting,
programming, management and even legal compliance to one’s profile are
some examples in this respect. Specializing in Mobile Development,
DevOps or Big Data has also been requested by various industries. During
the Q&A session, we broached the trend in Timisoara. From the
audience’s experience, Testers are currently learning how to write code,
while Developers are conducting more testing. Some companies are
experimenting with Test-Driven Development, while others favor employing
Automation Testers with JS.
It was a lively discussion and I felt
inwardly glad that I had selected such a varied range of topics at
CodeCamp 2017, that I could add to my technical kit and further explore.
Gamification
In addition to the various tracks, the
Code Campers had the opportunity to engage in various gamified
activities, designed by the partner companies present at the event.
During the breaks, you could take online quizzes on your topic(s) of
interest, dabble in Augmented Reality, try your hand in technical trivia
or participate in the Code Camp Raffle.
Bottom line: Apart from
dealing with the technical challenges prepared, you could also get to
know fellow campers and network. Which is what getting together on such
occasions is basically all about: experimenting in a safe environment,
exchanging best practices and keeping up-to-date with the most recent
trends.
Curious? Then just register here! You can also sign up as a Content Owner and prepare to share your experience with eager Code Campers! See you on April 21st!
If you check our meetup on November 9 we had set up our “usual” second Thursday of the month meetup just that it wasn’t usual at all… We celebrated 5 years of monthly meetups at Tabara de testare Bucuresti!!!
On the agenda for that evening we had the overview of the presentations/workshops we had during 2017 but this time we also prepared an overview of the previous years and afterwards we continued with the workshop on “Storytelling and communication” by Stefan Bratosin.
I’m going to start with Stefan’s workshop first because the 5 years part needs to be saved for last like all the good things.
Stefan’s workshop was inspired by some improvisation classes that he took and while being involved more and more in the classroom he realized how the exercises that he was doing could help other testers better communicate and be better story tellers since this is a big part of what we do.
The workshop had a lot of cool and fun exercises like:
The whole group had to count to 30 without anyone overlapping. The exercise was very interesting and we managed to count to 30 as a whole group(we were about 20) and without anyone overlapping. The “Aha” part of this exercise was when Stefan asked us to close our eyes and try this way to count to 30. We managed to listen and focus way better than the time we had our eyes opened and try to search each others all over the room and see who was the next one that will be going to say a number. We actually listened this time!
Question rally – something similar to “Whose line is it anyway” ( here is an example of the show with Whoopi Goldberg) where there were only questions. We were given a theme and we could answer only with a question. Really fun exercise in which we could see in action: open or closing questions, probing questions or rephrasing.
Another exercise from Stefan’s workshop showed us the difference between using “yes, and” and using “yes, but”. During the exercise we could notice that using “yes, but” was not at all constructive and at least during the exercise it was basically cutting off the conversation
In the story telling exercise we had to create a story and tell it as best as we could from a team of 5 volunteers point of view. It was really fun and again we could notice on how important is to listen to the other ones or things could derail quickly. An example of a story – “The New Year’s Eve “. Our team had to create a story and the main character was our friend “Georgica”. The twist of the exercise was that Stefan would point to us when we had to switch and take the role of the narrator. By the second team which tried telling the story they could notice that they have to better listen to their colleagues rather than focusing on what’s next so they can continue on what the story was all about. If you didn’t do that, in our teams story, the main character didn’t even make it to the new year’s eve party 🙂
Besides all the fun that we had during the workshop, we were reminded how important is communication and storytelling to our tester’s job so a big thank you to Stefan.
Here are some pictures from the exercises that we did:
5 years of Tabara de Testare Bucuresti
5 years means a lot of time but as they say “time flies when you’re having fun”.
So what we wanted to do different this time from the other anniversary editions is to try and summarise all the years, basically a trip down memory lane.
For me personally were the best slides I’ve worked on so far for the anniversary editions. It let me remember how we started, how many people helped us start, what we did these past years and of course how many we accomplished, in the end showing that we are truly a community of software testers and that without the people in it, we wouldn’t have anything.
Was really challenging to summarise all of the above (and many more) so we tried our best to do it through an infographic:
As you could see in the infographic there were 71 meetups in 60 months and we wanted to showcase the meetups in each year and for this we created gifs with pictures from them and verbally mention some of them since there were a lot to go through.
2012:
2013:
2014:
2015:
2016:
2017:
We couldn’t celebrate 5 years of Tabara de Testare Bucuresti without our traditional “Cartoon Tester” special cake . Here is also a big thank you for our supporters of this edition: ING Romania and QTeam Software Solutions which helped us with the cake and snacks/beverages.
What’s next?
That’s a really good question!!! I remember 5 years ago when we started having the meetups I was thinking: ”let’s start it and see where it goes”. Oh well, it went very good, so for the next 5 years I expect even more amazing things, even more cooler meetups, more international speakers, more people being content owners, more workshops during the years and the list could continue.
Not sure what’s next or could say specific how is going to be in the next 5 years, but I certainly know it’s going to be awesome since YOU ARE “TABARA DE TESTARE”!!! and knowing the amazing people that are members of this community there is no other way than an even greater journey in the years to come.
Esti Software Tester sau lucrezi intr-un domeniu conex? Iti doresti sa impartasesti altora din cunostintele tale? Atunci nu mai sta pe ganduri: Sustine un workshop in cadrul Taberei de Toamna!
Indiferent daca ai livrat deja numeroase sesiuni practice ori abia acum te familiarizezi cu vorbitul in public, aici poti sa te perfectionezi in continuare. Vei avea sustinerea noastra in pregatirea atelierului, precum si feedback, pentru a te prezenta cu o varianta imbunatatita la alte evenimente nationale si internationale.
Asemeni editiilor precedente, incurajam o abordare hands-on si te invitam sa participi la un experiment inedit, pe durata unui weekend prelungit.
De ce? Pentru ca editia 2017 sta sub semnul experimentarii cu diverse metode, abordari sau instrumente, intr-un cadru safe, care incurajeaza schimbul de experienta si invatarea continua, fara constrangerile unui produs anume ori a unui mediu de lucru specific.
Daca doresti sa ni te alaturi, completeaza acest formular si trimite-ne intre 01.09. si 10.09. propunerea ta pentru un atelier.
Spre sfârșitul anului trecut am răspuns unei serii de întrebări despre Tabăra de Testare într-un mini-interviu care a fost publicat pe evenimenteit.ro. Când a fost înfiițată Tabăra, care a fost motivația pentru crearea ei, care ar fi niște momente de care suntem mândri – doar câteva exemple de lucruri pe care le puteți afla despre noi, mai jos.
Care ar fi o scurtă descriere a grupului?
Tabăra de Testare este o comunitate formată din testeri și alți profesioniști din industria IT care, în cadrul unor întâlniri informale lunare, împărtășesc din cunoștințele proprii și învață din experiențele profesionale ale celorlalți membri.
Când a fost înfiițat grupul și care a fost motivația pentru crearea lui?
Primul pas a fost făcut în 2011. Alexandru Rotaru, unul dintre fondatori, participase la CAST, o conferință din Statele Unite organizată cu ajutorul voluntarilor, lipsită de caracter comercial, având ca scop schimbul de idei și experiențe între testeri. Pornind de la acest model, împreună cu o serie de voluntari, au avut loc primele evenimente Tabăra de Testare în București, Cluj, Iași și Timișoara în toamna lui 2011.
Scopul acestor evenimente a fost găsirea de oameni pasionați de testare care doresc să împărtășească din experiențele lor, să învețe din experiențele celorlalți și să contribuie la crearea unei “bresle” a testerilor în România.
Dintre participanții la aceste prime evenimente câțiva s-au arătat dispuși să se implice în formarea și dezvoltarea comunităților locale de testeri. Pe parcus, și alți testeri s-au alăturat în organizarea întâlnirilor. Așa s-au format și au crescut fiecare dintre cele 4 comunități locale.
Cui se adresează evenimentele grupului? (developer/manager, tehnologii folosite, nivel de experiență, …)
Evenimentele sunt făcute de testeri pentru testeri. Am descoperit că putem învăța lucruri valoroase și de la ceilalți colegi cu care interacționăm, așa că uneori avem ca invitați la întâlniri programatori, manageri de proiect, specialiști din zone conexe testării, în genere, profesioniști care activează în industria IT.
Nivelul de experiență nu este important pentru noi. Printre membrii noștri sunt testeri cu foarte mulți ani de experiență, încă dornici să învețe, dar și persoane care abia descoperă testarea.
De obicei unde, când și cât de frecvent se întâlnește grupul?
Fiecare Tabără dintre cele 4 are propriul calendar pentru întâlniri. Dezideratul nostru este să avem o întâlnire în fiecare lună, să ne întâlnim suficient de des cât să ne cunoaștem și să conturăm un mediu în care membrii au încredere să își împărtașească problemele de testare sau soluțiile găsite. Încrederea acesta este un ingredient pe care îl vedem esențial în dezvoltarea comunității.
Locurile în care au loc întâlnirile diferă. Cele mai multe sunt spații informale (de tipul co-work, cafenele, terase), tocmai pentru a beneficia de o atmosferă mai relaxantă, colaborativă, propice învățării.
Comunitatea națională se reunește anual într-o tabără la munte. De 4 ani mergem toamna la o cabană, într-o tabără “testărească”, unde avem ateliere, multă interacțiune și schimb de experiență. Această tabără este deja cunoscută sub numele de Tabăra de Toamnă și cele mai recente ediții au ținut două zile jumătate.
Care este momentul din viața grupului de până acuma de care ești cel mai mândru?
Probabil fiecare dintre cei implicați în organizarea Taberei de Testare are un moment preferat. Cred însă că mai mulți ar nominaliza cea mai recentă Tabăra de Toamnă. Acest eveniment a evoluat în 4 ani de la o întâlnire de un weekend, în preajma Clujului, cu 3 sau 4 sesiuni și 20-30 de participanți, la un eveniment cu track-uri paralele, cu 20 de content owner-i și 70 de participanți din toată țara. Momentul de glorie în organizarea ediției de anul acesta l-am resimțit atunci când ne-am dat seama că membrii se înscriau “în alb“, fără să știe agenda, bazându-se pe experiențele de la edițiile trecute sau pe recomandările prietenilor, colegilor. Glumeam pe seama asta, că noi știam că doar la Electric Castle se mai vând biletele fără să fie anunțat line up-ul.
Ceva planuri de viitor super-secrete pe care ne poți dezvălui în exclusivitate? 🙂
Nu putem dezvălui planurile ultra-secrete, dar putem dezvălui o surpriză pe care o pregătim. James Bach, unul dintre cei mai cunoscuți testeri, a fost în Cluj zilele trecute și ne-a acceptat invitația de a ține o prezentare pentru comunitate. 200 de participanți au fost prezenți la meetup-ul cu el. Credem că mult mai mulți și-ar fi dorit să participe. Ce am reușit să facem pentru ei a fost să înregistrăm sesiunea. Astfel, curând vom putea face disponibilă pentru întreaga comunitate de testeri prezentarea lui despre analiza de risc în testare. (Later edit: între timp, am publicat-o aici.)
Care este motivul principal pentru care cineva ar trebui să participe la întâlnirile grupului?
Nu este imperios pentru nimeni să participe. Dar testerilor care sunt (ne place nouă să spunem) într-un mod de învățare continuă le putem da două motive. Primul este conținutul sesiunilor, din care pot învăța lucruri inedite sau pot deprinde abilități noi, de la cele mai tehnice la cele din categoria soft skills. Acoperim o varietate de subiecte, în formate diverse, de la prezentări și ateliere pe teme de testare sau tangente acesteia, la sesiuni ludice de învățare ori “clinici de testare”. Și pentru că vorbim de o comunitate, al doilea motiv ar fi că participanții vor cunoaște oameni noi, cu cel puțin o pasiune comună și o perpectivă diferită.
Unde pot cei interesați să afle mai mult despre grup? (site, Facebook, twitter, etc)
Întâlnirile lunare de la Tabăra de Testare sunt organizate pe Meetup, o platformă dedicată pentru organizarea evenimentelor. Pentru a participa la astfel de întâlniri, doritorii trebuie să se înscrie în grupul din orașul lor, după care vor primi notificări atunci când sunt anunțate întâlniri. Grupurile sunt:
Ce alte gânduri ai vrea să transmiți cititorilor evenimenteIT.ro?
Noi, cei care lucrăm în IT, beneficiem de multe posibilități de învățare continuă, în comparație cu alte industrii. Să fructificăm aceste oportunități!
Meetup-ul din octombrie 2016 de la Tabara de Testare Cluj a fost unul special: content owner a fost James Bach care a tinut o prezentare despre Risk Analysis in Software Testing.
In pregatirea pentru cursurile pe care le tine pentru testeri, James a incercat cu participantii un exercitiu privind riscurile, analiza lor si implicatiile pe care le au in testare. James si participantiiau cautat i dei de test pentru o masina autonoma de nivel 4, apoi au comparat notitele. Ce a iesit? Va lasam sa descoperiti singuri:
