Testing Challenge #7 was completed by



  • FredVasilescu

    The words were:

    Project Manager / Security / Context Driven Testing / eXtreme Programming

    The story:

    My Project Manager is a big fan of Security. He is very paranoid about security. He calls it caution. You might be wondering what kind of project he is leading, well, it's Context Driven Testing at a Security Firm. eXtreme Programming is when you drink 3 redbulls, listen to nightcore and code in binary.
  • RaAl

    The words were:

    Business Analyst / Integration Testing / Pair Testing / Agile Principles

    The story:

    Today i will start reading the Agile Principles and learn how to make the Pair Testing .because i need to do another test ,not only the Integration Testing ,Once I finished the Business Analyst.
  • Predrag

    The words were:

    Project Manager / Cause And Effect Testing / Combinatorial Testing / eXtreme Programming

    The story:

    I am working as Project Manager for 6 years. At my work I was dealing, with Cause And Effect Testing, Combinatorial Testing, extreme Programming.
  • Predrag

    The words were:

    Tester / Error Handling / Ad Hoc Testing / Conference

    The story:

    Predrag Miličević , – Curriculum Vitae. Work experience - Tester. My interests - error Handling, ad Hoc testing, conference
  • Predrag

    The words were:

    Business Analyst / System Testing / Data Driven Testing / Planning Meeting

    The story:

    I am Business Analyst. I am specialized in system testing, data driven testing and planning meeting.
  • Khushali Virdikar

    The words were:

    / / /

    The story:

  • Bob

    The words were:

    Customer / Component Testing / Model Based Testing / Review Meeting

    The story:

    Customer Component Testing Model Based Testing Review Meeting
  • Urtzely

    The words were:

    Business Analyst / Domain Testing / Behaviour Driven Development / Agile Principles

    The story:

  • Pooja Shah

    The words were:

    Customer / Compliance Testing / Context Driven Testing / eXtreme Programming

    The story:

    The Customer is waiting, we got to have the product ready in a week. To release faster and catching bugs early, let's do Unit Testing first and see the coverage and Pair testing to find and fix the bugs immediately. If we are still not having confidence on the quality of our delivery, let's take Community's support to do beta testing at-least before two days of the release. Release plan 1. Compliance Testing 2. Context Driven Testing 3. eXtreme Programming
  • Dmitry

    The words were:

    Product Owner / Localization / Behaviour Driven Development / Agile Manifesto

    The story:

    Dear Product Owner. Our team hane done the localization testing for a project. On the nexn weak we are going to start new features, and to prepare Behaviour Driven Development. How are we trying to do that - we let's start Agile Manifesto.
  • kushalgnaik11@gmail.com

    The words were:

    Test Manager / Test Automation / Behaviour Driven Development / Daily Scrum

    The story:

    Today the test manager in our daily scrum meeting noted that some cases in Test Automation done by the team were not related to the Behaviour Driven Development requirement.
  • Tushar

    The words were:

    Test Manager / Decision Table Testing / Exploratory Testing / SCRUM

    The story:

    Testing is essential for a software product to be bug free. A Test Manager gives his instructions to the junior testers and makes decision table testing.EXPLORATORY TESTING is a type of software testing where Test cases are not created in advance but testers check system on the fly. They may note down ideas about what to test before test execution.Scrum is a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal.The decision table is a software testing technique which is used for testing the system behavior for different input combinations.
  • Justyna

    The words were:

    Agile Coach / Compliance Testing / Crowd Testing / Training

    The story:

    An Agile Coach invited us to a Compliance Testing Training but I had no idea what does it mean so I went to Crowd Testing forum and read about it.
  • Olly

    The words were:

    Developer / State Transition / Ad Hoc Testing / Budget Meeting

    The story:

    Wow! Developer, State Transition, Ad Hoc Testing Budget Meeting
  • konrad

    The words were:

    Project Manager / Operational Readiness / Model Based Testing / Daily Scrum

    The story:

    during the daily scrum our project manager spoke of operational readiness and model based testing
  • rajat

    The words were:

    Tester / Decision Table Testing / Exploratory Testing / Review Meeting

    The story:

    Tester not only tests the application but also performs decision table testing and exploratory testing once the review meeting is over.
  • hilda

    The words were:

    Tester / Fuzz Testing / Acceptance Testing / Tutorial

    The story:

    Tester Fuzz Testing Acceptance Testing Tutorial
  • slavaa

    The words were:

    Administrator / User Experience / Exploratory Testing / Community

    The story:

  • ataeva.hanna.1993@gmail.c

    The words were:

    Tester / Boundary value analyses / Data Driven Testing / eXtreme Programming

    The story:

    If we use extereme programing metodology in software development the tester have to provide data driven testing and boundary value analyses.
  • Katelyn

    The words were:

    Test Manager / Localization / Context Driven Testing / Tutorial

    The story:

    You have to make a tutorial for a localization app, using context driven testing, then your tutorial will be approved by test manager of your team.
  • Danil Saikin

    The words were:

    Customer / Compliance Testing / Exploratory Testing / Estimation Meeting

    The story:

    On Estimation Meeting Customer wanted to know what Compliance Testing and Exploratory Testing are.
  • 555

    The words were:

    Administrator / Domain Testing / Behaviour Driven Development / Review Meeting

    The story:

  • Bohdan

    The words were:

    Business Analyst / Localization / Alpha Beta Testing / Waterfall model

    The story:

    A business analyst speaks with a customer to the waterfall methodology, explains how work will be done to localize his product, localization testing will be done by alpha beta testing after developers work on this product
  • jkomp

    The words were:

    Business Analyst / Test Automation / Test Driven Development / SCRUM

    The story:

    SCRUM is a framework often used in the development world for creating complex products. SCRUM rests on certain guidelines to ensure the process runs smoothly. Two of these guidelines are Test Automation and Test Driven Development. Test Automation allows for a much quicker and broader testing capacity since computers can take care of much of the actual computational and processing work. Test Driven Development is a process where tests for software are written beforehand according to the specifications of the project, rather than coming up with them after the development process is already finished. In SCRUM, there are many roles, and Business Analyst is one of those roles that often acts as a customer liaison to get the specifications from the customer to give to the engineering team so they can do their development.
  • Jusha

    The words were:

    Scrum Master / Component Testing / Code DrivenTesting / Retrospective Meeting

    The story:

    In the Retrospective Meeting ,the Scrum Master has suggested the team to include Code DrivenTesting and Component Testing
  • tnj86

    The words were:

    Project Manager / Security / Combinatorial Testing / Retrospective Meeting

    The story:

    Project Manager is fine. Security was broken. We are usin' Combinatorial Testing. Tomorrow is Retrospective Meeting.
  • Florian Rus

    The words were:

    Customer / Security / Agile Testing / Planning Meeting

    The story:

    we were going to have a planning meeting with our customer before starting the agile testing but we realized during the documentation inspection that the application had a security issue that needs to be discussed and fixed
  • Dimo Gkriziotis

    The words were:

    Project Manager / Decision Table Testing / Combinatorial Testing / Software Crafsmanship

    The story:

    The Project Manager for the current test uses a decision table testing is a software testing technique used to test system behavior for different input combinations. Due to multiple configuration parameters we will use Combinatorial testing which is an effective technique to test software with such aspects. The automation approach is the current that will be applied so the to be according to the rules of Software craftsmanship that emphasizes the coding skills of the software developers.
  • Alex Owner

    The words were:

    Project Manager / Cause And Effect Testing / Crowd Testing / Budget Meeting

    The story:

    Project Manager, Cause And Effect Testing, Crowd Testing, Budget Testing - these words are from testing
  • Neda Stefanova

    The words were:

    Developer / Portability / Exploratory Testing / Planning Meeting

    The story:

    I am a Developer. I testing Portability. I do Exploratory Testing. My responsibility is Planning Meeting.
  • LUKAS PU

    The words were:

    Administrator / Performance / Test Driven Development / eXtreme Programming

    The story:

    administrator performance test driven development.
  • Yurii Pokryshkin

    The words were:

    Business Analyst / Boundary value analyses / Combinatorial Testing / SCRUM

    The story:

    Business Analyst Boundary value analyses Combinatorial Testing SCRUM
  • Andrey

    The words were:

    Project Manager / Operational Readiness / Crowd Testing / Planning Meeting

    The story:

    Project Manager Operational Readiness Crowd Testing Planning Meeting My training has just begun, so maybe later. Thank!
  • Alexander Antipyev

    The words were:

    Scrum Master / Cause And Effect Testing / Testability / Software Crafsmanship

    The story:

    Scrum Master Cause And Effect Testing Software Crafsmanship Testability
  • 34

    The words were:

    Agile Coach / Test Automation / Crowd Testing / Training

    The story:

  • Viktor

    The words were:

    Developer / Test Automation / Context Driven Testing / Review Meeting

    The story:

    A developer, who was about to start a course in 'Test Automation', is late to his classes. He was stuck at home working on Context Driven Testing chapter of his course book. He totally lost track of time. What he also forgot about was, that there was a Review Meeting with his lecturer right before the class and he was supposed to attend it. So now he is gonna be in trouble.
  • Zandreika

    The words were:

    Customer / Compatibility / Ad Hoc Testing / Waterfall model

    The story:

    My story about Customer so long. I don't want to write down so many words about Compatibility or something else. Yes, I did Ad Hoc Testing, and working on Waterfall model, of course
  • Andrew Simpson

    The words were:

    Project Manager / Component Testing / Combinatorial Testing / Agile Principles

    The story:

    Project managers should have a basic understanding of software testing including the different levels at which testing can occur (e.g. component testing). If their project is following an agile approach then one would hope that the project manager also has a good understanding of the Agile principles. I wouldn't think it necessary for the project manager to understand low-level test techniques such as combinatorial testing techniques though.
  • Karpov Egorka

    The words were:

    Project Manager / Performance / Behaviour Driven Development / Review Meeting

    The story:

    Project Manager Performance Behaviour Driven Development Review Meeting
  • Anna Zakiryanova

    The words were:

    Developer / Compliance Testing / Combinatorial Testing / Conference

    The story:

    Developer Compliance Testing Combinatorial Testing Conference
  • Alexander Goryushkin

    The words were:

    Project Manager / Cause And Effect Testing / Alpha Beta Testing / Agile Manifesto

    The story:

    Way this challenge? As testers we have to come up with scenarios .We have to imagine them based on the information we have. Scenarios are like stories. This challenge helps you practice your story telling. Your challenge is to imagine and write (in English) a story, that has meaning, with the words bellow. You have 20 minutes to do so. The text will be validated if it contains the words required before submitting. It will be reviewed afterwards if it has any meaning. Your words are: Project Manager Cause And Effect Testing Alpha Beta Testing Agile Manifesto
  • Petrosyan Loris

    The words were:

    Product Owner / Test Automation / Behaviour Driven Development / Budget Meeting

    The story:

  • Stu

    The words were:

    Project Manager / User Experience / Code DrivenTesting / Planning Meeting

    The story:

    The Project Manager used the User Experience to provide Code DrivenTesting for the Planning Meeting.
  • beltriks

    The words were:

    Project Manager / Error Handling / Behaviour Driven Development / Training

    The story:

    Project Manager Error Handling Behaviour Driven Development Training
  • Vitaly

    The words were:

    Business Analyst / Unit Testing / Crowd Testing / Agile Principles

    The story:

    I am a Business Analyst. My work is a Unit Testing and Crowd Testing. i am use Agile Principles in my work.
  • Dasha V

    The words were:

    Test Analyst / Localization / Rapid Testing / Review Meeting

    The story:

    As a Test Analyst, I come many test scenatio every day. As for Localization. In the process of Rapid testing, I go through the location in the main forms.I will be glad to hear a list of the forms which must be checked for localization testing
  • Dasha Velmakina

    The words were:

    Project Manager / Domain Testing / Rapid Testing / Agile Manifesto

    The story:

  • Tanya Skakun

    The words were:

    Scrum Master / Component Testing / Behaviour Driven Development / Review Meeting

    The story:

    Our team decided on choosing Ann as Scrum Master for our next Scrum Poker game. We think, it's going to help to improve our component testing process. Our main next step will be focusing more on the behaviour driven development. The results of all the planning will be presented on the review meeting next month.
  • Vasili Shastsiyuk

    The words were:

    Product Owner / Unit Testing / Model Based Testing / Conference

    The story:

    This is water. Product Owner of this water is Coca-Cola. We need to write program for them. In this program we need to use Unit Testing and Model Based Testing. Results will be presented on Conference.
  • Eugene

    The words were:

    Scrum Master / Portability / Context Driven Testing / Daily Scrum

    The story:

    As a Scrum Master you have to support a Portability, since a Context Driven Testing requires a Daily Scrum meetings.
  • Yuliya

    The words were:

    Test Manager / Error Handling / Code DrivenTesting / eXtreme Programming

    The story:

    Test Manager Code DrivenTesting Error Handling eXtreme Programming
  • AndraB

    The words were:

    Business Analyst / Performance / Agile Testing / SCRUM

    The story:

    You are running an agile testing and the scrum master is telling you to finish the performance test in the next week as scheduled. The business analyst has discussed with the scrum master and the other testers and the performance test should go on as planned.
  • Nikolay

    The words were:

    Administrator / Unit Testing / Crowd Testing / Training

    The story:

    After many years of programmers' work, a new game client was released . its main advantage is portability. When testing the product, we used unit testing, but after the release in production, the administrator began to receive complaints about the client 's work. The product passed all the tests on the stands without a single failure. It was not possible to expand the test coverage, and the company's resources were limited. It was decided to use crowd testing. All the company's specialists gathered and started conducting training.
  • ptrck

    The words were:

    Project Manager / Integration Testing / Context Driven Testing / Community

    The story:

    As a Project Manager, i would like this application to provide me a monthly summed up data, given that i input my daily costs. In order to provide a good testing metrics, we should consider performing Integration Testing over this application. Another approach for good testing coverage could be Context Driven Testing. As for acceptance and customer testing, i believe that the best what we could do is to provide beta version to the Community, and ask for opinions.
  • Kate

    The words were:

    Agile Coach / User Experience / Data Driven Testing / Agile Principles

    The story:

  • Kate

    The words were:

    Agile Coach / Localization / Alpha Beta Testing / Tutorial

    The story:

    Your words are: Agile Coach Localization Alpha Beta Testing Tutorial
  • Kate

    The words were:

    Scrum Master / Decision Table Testing / Agile Testing / Agile Manifesto

    The story:

    Your words are: Scrum Master Decision Table Testing Agile Testing Agile Manifesto
  • D

    The words were:

    User / Error Handling / Pair Testing / Software Crafsmanship

    The story:

  • Kirill Kurochka

    The words were:

    Business Analyst / Error Handling / Pair Testing / Tutorial

    The story:

    Business Analyst conducted a market analysis for the relevance of the ideas of our new product, which is associated with the improvement of the current clothing sales algorithms. Having received satisfactory results about the high interest of consumers in the tools we promote, a detailed business plan was drawn up, after which the project was given to developers for development. Timing, as always, was running out. Programmers, having forgotten about unit-tests, tried to catch everything by dead-line. Scrum was chosen as the framework for our rather complex concept. In the shortest time, our online service was created. Testers took up the matter. Conducting a bunch of tests, which included a variety of user interface checks, database interactions, various payment methods, and other types of Data Driven Testing. Pair testing was also performed for greater accuracy. Thanks to the attentiveness and integrity of the testers, it was possible to identify a number of serious bugs before the release. Error Handling has been ongoing. Upon completion of all tests, a Tutorial was created to work with this service. The first users who used our service were delighted with the improved mechanism for buying clothes on our website.
  • Nataliia

    The words were:

    Business Analyst / Performance / Crowd Testing / Training

    The story:

    Once upon a time brilliant Business Analyst decided start smoking. It was just before his Performance at the Opera stage. The day before his turning point his mother was ordered to take Crowd Testing. But as responsible son he could not accept such Training
  • asd

    The words were:

    Administrator / Unit Testing / Data Driven Testing / eXtreme Programming

    The story:

    You are Administrator you need to create Unit Testing for app. Always we use Data Driven Testing. Part of our QA is eXtreme Programming
  • Jerry Herrera

    The words were:

    Customer / Domain Testing / Exploratory Testing / eXtreme Programming

    The story:

    As a Customer, one important thing that can help is the knowledge of Domain Testing and Exploratory Testing, this can be achieved if the customer is involved in a team using eXtreme Programming
  • Tally Wilsher

    The words were:

    Product Owner / Domain Testing / Agile Testing / Training

    The story:

    Product Owner as about out Domain Testing knowledge. As a Agile Tester and having no formal training in Domain Testing it as explained to the product owner that Agile Testing would be the preferred methodology for this epic.
  • Edirin

    The words were:

    Project Manager / System Testing / Test Driven Development / Daily Scrum

    The story:

    The Project Manager insisted System Testing must be done to ensure we meet the regulatory requirements. The team currently practices Test Driven Development as part of the workflow with discussions happening about it constantly at the Daily Scrum.
  • Shubhanshi

    The words were:

    Tester / Operational Readiness / Model Based Testing / eXtreme Programming

    The story:

    The product being developed has followed an extreme programming approach, here we have set small goals for each team and reviewed the code as we go along each stage of the Software development life cycle. Frequent meetings have been conducted to decide on new strategies and keep a track of the current progress because the extreme programming approach is chaotic in general. The tester is charge has to test the model in order to verify the specifications are being met. This process has to be done hand-in-hand with the software development because testing done directly at the end of the project may prove catastrophic for the project. One such feasible approach for testing is model based testing which is conducted based on the model implemented while development such as agile , waterfall, etc. Consider we have the spiral model, the tester will have to iteratively check the system progress for stages such as requirements gathering and project implementation. Model based testing considers the non functional parts of the product being tested, other than that functional testing using tools like Selenium will be conducted. At the end of development, the product should be ready for operation and there should not be any known bugs or risks associated. Tester needs to ensure operational readiness of the system, i.e an overall operational readiness testing should be conducted which includes testing all the functional and non functional parts of the system before it can be deployed.
  • /dev/null

    The words were:

    Agile Coach / Portability / Acceptance Testing / eXtreme Programming

    The story:

    I did a challenge writing a story that has meaning and contains the words required for submitting: Agile Coach, Portability, Acceptance Testing, eXtreme Programming.
  • Gytis

    The words were:

    Administrator / Localization / Agile Testing / Tutorial

    The story:

    Once upon a time an administrator was practicing agile testing while watching a tutorial on YouTube. His localization was set by Google.
  • Lana

    The words were:

    User / Happy Path Testing / Ad Hoc Testing / Agile Principles

    The story:

    Our company is based on Agile Principles - that is mean - happy User is over the contract negotiation. Also we use not only Happy Path Testing but Ad Hoc Testing in goal with increasing the test cover.
  • Stanley

    The words were:

    Administrator / Decision Table Testing / Data Driven Testing / Estimation Meeting

    The story:

  • Stanley

    The words were:

    User / Happy Path Testing / Acceptance Testing / Training

    The story:

  • Landon

    The words were:

    Test Manager / Compliance Testing / Ad Hoc Testing / Waterfall model

    The story:

    Test Manager Compliance Testing Ad Hoc Testing Waterfall model
  • Anitha Balasundaram

    The words were:

    Administrator / Performance / Alpha Beta Testing / Training

    The story:

    Administrator can have one or more logins Performance of the application need o be double check if there is more data Application is under Alpha beta testing Training column in the application need to be retested
  • Oleksandr

    The words were:

    Tester / Happy Path Testing / Test Driven Development / Budget Meeting

    The story:

    At a Budget Meeting Tester suggested using Happy Path Testing and Test Driven Development
  • Ulf

    The words were:

    Test Manager / Unit Testing / Rapid Testing / Training

    The story:

    As Test Manager I have to ensure that testing take place on all test Levels inluding Unit Testing. Therefore I have to Setup a Trainng for Rapid Testing.
  • Viacheslav Kuzin

    The words were:

    Customer / Performance / Testability / Tutorial

    The story:

    Customer Performance had always loved magical Dallas with its encouraging, elegant estuaries. It was a place where he felt sleepy. He was a virtuous, hilarious, beer drinker with ample moles and hairy arms. His friends saw him as a talented, tame teacher. Once, he had even made a cup of tea for a regurgitated toddler. That's the sort of man he was. Customer walked over to the window and reflected on his sunny surroundings. The hail pounded like loving lizards. Then he saw something in the distance, or rather someone. It was the figure of Testability Tutorial. Testability was a scheming wally with red moles and tall arms. Customer gulped. He was not prepared for Testability. As Customer stepped outside and Testability came closer, he could see the warty glint in his eye. Testability gazed with the affection of 2795 bold great guppies. He said, in hushed tones, "I love you and I want a kiss." Customer looked back, even more stable and still fingering the crumpled sandwich. "Testability, let's move in together," he replied. They looked at each other with fuzzy feelings, like two cooperative, charming cats thinking at a very cowardly Valentine's meal, which had jazz music playing in the background and two gracious uncles jumping to the beat. Customer regarded Testability's red moles and tall arms. "I feel the same way!" revealed Customer with a delighted grin. Testability looked stable, his emotions blushing like a kindhearted, kooky knife. Then Testability came inside for a nice drink of beer. THE END
  • Larisa

    The words were:

    Product Owner / System Testing / Acceptance Testing / Review Meeting

    The story:

    The Product Owner decide to spend system testing. The acceptance testing improved. Currently we are spending review meeting.
  • Abhi

    The words were:

    Tester / Install Uninstall Testing / Acceptance Testing / Waterfall model

    The story:

    As a Tester, I need to validate the installation of the developed app. So that the scope of this story is basically to perform Install Uninstall Testing. Once the testing is complete then the story must be handed over to the business owner in order to perform the Acceptance testing. We are going to execute this process in Waterfall model
  • Pavel Novikov

    The words were:

    Tester / Fuzz Testing / Pair Testing / Waterfall model

    The story:

    When moving from the Waterfall model to Agile, the manager made it a task for the Tester to learn a few additional types of testing: Fuzz Testing, Pair Testing and so on.
  • Inesa

    The words were:

    Tester / Fuzz Testing / Context Driven Testing / Planning Meeting

    The story:

    As a tester, we should many approaches in order to identify potentials issues. As a first step, we should have a planning meeting to prioritize the scenarios to have a relevant Context Driven Testing, also we have a fuzz testing as early as possible to identify the coding issues.
  • sad

    The words were:

    Administrator / Install Uninstall Testing / Data Driven Testing / Review Meeting

    The story:

    I appointed Review Meeting with Administrator to disscus Data Driven Testing and Install Uninstall Testing.
  • Agustin Pequeno

    The words were:

    Scrum Master / Unit Testing / Model Based Testing / Training

    The story:

    As a scrum master, I want to allow my development team to perform more unit testing and improve there model based testing through training
  • Daria

    The words were:

    Customer / Compliance Testing / Crowd Testing / Agile Manifesto

    The story:

    Once upon a time one customer desides to buy a copy of Agile Manifesto. But there was a problem: there were a lot of people who wanted to do the same. "Hey", said the shop owher. "If you all made a crowd testing for my new feature, I'll give you copies for free". Everybody agreed. Everybody except our customer. "I'll do compliance testing. This is my manifesto".
  • Silvia

    The words were:

    Test Manager / Error Handling / Combinatorial Testing / eXtreme Programming

    The story:

    Given Error Handling, and extreme programming, when Combinatorial testing is good, then test manager has to check.
  • kjkj

    The words were:

    Administrator / Performance / Exploratory Testing / eXtreme Programming

    The story:

    Administrator, Performance, Exploratory Testing, eXtreme Programming.
  • lmm

    The words were:

    / / /

    The story:

  • Jesus Christ

    The words were:

    Administrator / Security / Behaviour Driven Development / Waterfall model

    The story:

    Administrator Security Behaviour Driven Development Waterfall model
  • Anastasia Moreva

    The words were:

    Scrum Master / Integration Testing / Exploratory Testing / SCRUM

    The story:

    Once upon a time, our Scrum Master asked the team at Sprint Retrospective how the quality of the product would improve if we started to use not only Exploratory Testing, but also Integration Testing. Then we created an action item for research this question
  • Klevzoff

    The words were:

    Test Analyst / User Experience / Testability / Daily Scrum

    The story:

    Test Analyst during the Daily Scrum reports about Testability, using his User Experience in product.
  • irina

    The words were:

    Test Analyst / User Experience / Acceptance Testing / Retrospective Meeting

    The story:

    I, as Test Analyst want to gather User Experience, because it help our team to use Acceptance Testing on Retrospective Meeting
  • TADEK

    The words were:

    Customer / User Experience / Ad Hoc Testing / SCRUM

    The story:

    As a customer with my user experience, I need ad hoc testing from my testers which work in SCRUM
  • Zoe White

    The words were:

    Scrum Master / Compliance Testing / Testability / Training

    The story:

    The scrum master decided the team needed training to improve the testability of their stories. The compliance testing usually passed, as the testing affirmed the acceptance criteria for the most part, but the team as a whole missed stuff, and things were either hard to test or invisible to the testers.
  • StanislavPasanov

    The words were:

    Agile Coach / User Experience / Exploratory Testing / SCRUM

    The story:

    agile Coach, user experience, exploratory Testing, SCRUM
  • Rachel Kibler

    The words were:

    Business Analyst / Error Handling / Crowd Testing / Budget Meeting

    The story:

    The Business Analyst wants to reduce the cost of internal testing and has decided to outsource this to Crowd Testing. Using a platform to report bugs, we will give ideas to trigger errors so we can check our Error Handling. We want to make sure that errors are reported correctly through logging, and that the users don't see nonsensical errors. Thus, we will give fail conditions and ask people to validate that they see the right errors at the right time, also validating that we don't see odd or uncaught errors in our backend. The Business Analyst presented this at the Budget Meeting, and the budget for Crowd Testing was approved.
  • Dileepa

    The words were:

    Tester / Install Uninstall Testing / Acceptance Testing / Review Meeting

    The story:

    normally testers for install uninstall testing and acceptance testing
  • Evgheni C.

    The words were:

    Scrum Master / User Experience / Pair Testing / Planning Meeting

    The story:

    1.Validate that can access the Scrum Master 2.Check if User Experience is present 3.Check if Pair Testing can be done 4.check if we are able to have a Planning Meeting
  • Shuaib Kunji

    The words were:

    Test Analyst / Boundary value analyses / Crowd Testing / Daily Scrum

    The story:

    As a test analyst I come across many interesting scenarios in my day to day life. I have to put myself in the mind of the customer who uses the application and imagine the common mistakes he/she might make. As a failsafe I have to employ Boundary value analyses which help me as practically, due to time and budget considerations, it is not possible to perform exhausting testing for each set of test data, especially when there is a large pool of input combinations. If time is a constraint, then crowd testing might be a necessity too. A great example of this is beta testing wherein a pre-release version of the application is released to the beta-testers for free so they can report the flaws they notice or experience. Sometimes we have to participate in Daily Scrum which is a time boxed event. Here, the development team coordinates and comes up witha a plan for the next 24 hours. However the Daily Scrum is mistaken for a status meeting which it definitely isn't.
  • tal talman

    The words were:

    User / Portability / Rapid Testing / SCRUM

    The story:

    One day there was a User named Test. Test was asked to be a part of a SCRUM team for all of their testing needs. Test would show the portability of the mobile devices and laptop's used during rapid testing.
  • Hassyyy

    The words were:

    Business Analyst / Operational Readiness / Acceptance Testing / Budget Meeting

    The story:

    Why this challenge? As testers, we have to come up with scenarios. We have to imagine them based on the information we have. Scenarios are like stories. This challenge helps you practice your story telling. Your challenge is to imagine and write (in English) a story, that has meaning, with the words below. You have 20 minutes to do so. The text will be validated if it contains the words required before submitting. It will be reviewed afterwards if it has any meaning. Your words are: Business Analyst Operational Readiness Acceptance Testing Budget Meeting
  • Alex

    The words were:

    Agile Coach / Error Handling / Code DrivenTesting / Tutorial

    The story:

    Agile Coach has prepared a Tutorial which teaches Error Handling and Code DrivenTesting.
  • Daniela

    The words were:

    Project Manager / Component Testing / Model Based Testing / Review Meeting

    The story:

    The project manager suggest to do a fiew component testing for the complete application because most of the users have several mistakes; that´s why we have to follow a Model Based Testing to have an order of all the test cases to show them to the final users at the Review metting that we gonna have next Monday.
  • Eva

    The words were:

    Developer / Operational Readiness / Rapid Testing / Retrospective Meeting

    The story:

    AS A DEVELOPER I HAVE TO ASSURE THE OPERATIONAL READINESS, SO THE QA MAKE RAPID TESTING AND THE RESULT IS THAT WE HAVE NO ISSUES TO DISCUSS AT THE RETROSPECTIVE MEETINGS
  • Natalia M

    The words were:

    Project Manager / Component Testing / Agile Testing / Agile Principles

    The story:

    As a project manager I have no idea how component testing is done. Instead I know that agile testing is a testing methodology which helps quickly bring a quality product to the market without loosing money and time. Following agile principles is the best way to make a developer get mad ;)
  • YairM

    The words were:

    Test Manager / Unit Testing / Data Driven Testing / Agile Manifesto

    The story:

    Dan was a Test Manager experienced in Unit Testing and Data Driven Testing. One day he read the Agile Manifesto. The End.
  • izzmajjra

    The words were:

    Product Owner / Cause And Effect Testing / Testability / Review Meeting

    The story:

    Product Owner Cause And Effect Testing Testability Review Meeting
  • Eliana Montaña Conti

    The words were:

    Administrator / System Testing / Pair Testing / Agile Manifesto

    The story:

    As an Administrator i need to be able to work on System Testing and Pair Testing, for Agile Manifesto.
  • Eliana

    The words were:

    Developer / Fuzz Testing / Pair Testing / SCRUM

    The story:

    As a Developer i need to de able to use fuzz testing and pair testing, for any a scrum project.
  • Amogh

    The words were:

    Developer / Localization / Combinatorial Testing / Tutorial

    The story:

    Once there was a group of college students. They had a thought of developing a software which is helpful for milenials. They had some Developer with to start the implementation. But due to lots of globalized system, they wanted something which might promote more Localization .But to test the system at lower cost and in effective manner they used Combinatorial Testing . So now they started teaching other how to use by conducting Tutorial .
  • Dark

    The words were:

    Customer / Error Handling / Test Driven Development / Planning Meeting

    The story:

    On the planninng meeting our team decided to use test driven development and error handling to satisfy the customer.
  • Topher Hindman

    The words were:

    Administrator / Performance / Data Driven Testing / SCRUM

    The story:

    As an administrator of an agile SCRUM team, I need to measure the performance of my internal application and validate, via data driven testing, that the load the server's will have under peak traffic will not cause the application to run slowly for our colleagues.
  • ekaterina

    The words were:

    User / Error Handling / Acceptance Testing / Estimation Meeting

    The story:

    One time the User, who should do Error Handling, thought about Acceptance Testing. He had held a Estimation Meeting yesterday and wanted use Remaining time for something useful
  • ekaterina

    The words were:

    User / Error Handling / Acceptance Testing / Estimation Meeting

    The story:

    One time the User, who should do Error Handling, thought about Acceptance Testing. He had held a Estimation Meeting yesterday and wanted use Remaining time for something useful
  • Muhajir Akbar

    The words were:

    Product Owner / Domain Testing / Testability / Training

    The story:

    - As Muhajir, I want to be a product owner, so I can have better knowing about business flow a application. - As Muhajir, I want to do Domain Testing, so I can validate the integrity of input values. - As Muhajir, I want to make sure the application have testability, so I can easily testing the application. - As Muhajir, I want to training about automation testing, so I can be a good QA engineer.
  • Cobalt

    The words were:

    Agile Coach / Test Automation / Context Driven Testing / Waterfall model

    The story:

    The Agile Coach gives us the basic approach of test automation with Context Driven testing, which is very different from the Waterfall model.
  • Dmitry

    The words were:

    Customer / Performance / Exploratory Testing / Planning Meeting

    The story:

    On our Planning Meeting we forgot to allocate time and resources for Performance testing, so when our Customer started UAT with simple Exploratory Testing using 20 PCs simultaneously our product crashed.
  • bobby

    The words were:

    Test Analyst / Install Uninstall Testing / Crowd Testing / Budget Meeting

    The story:

    As a Test Analyst, I'd like to perform Install Uninstall Testing and Crowd Testing in preparation for the Budget Meeting
  • SUNIL NEGI

    The words were:

    Developer / Boundary value analyses / Agile Testing / Community

    The story:

    Verify the developer has first done the boundary value analyses and through the agile testing tester provides the best product to a different community.
  • Naduha

    The words were:

    Tester / User Experience / Context Driven Testing / Agile Principles

    The story:

    Today's day at work was very interesting and challenging. As you know, I'm currently working as a tester on a new project. This is the first project I work on which uses the SCRUM, which is one of the Agile methodologies and I must say it's really awesome! Agile principles is just what my work lacked all this time. One of the most important practices we have is Context Driven Testing, which is much less boring as I expected it to be. Using this methods and this kind of testing we are really gonna make sure that the User Experience will be just wonderful. The world can't wait to see our magic app!
  • Interlet

    The words were:

    Agile Coach / Compliance Testing / Alpha Beta Testing / SCRUM

    The story:

  • Interlet

    The words were:

    Customer / Error Handling / Crowd Testing / Conference

    The story:

    During conference logged customer should be able to avoid error handling in case of crowd testing
  • Manpreet kaur

    The words were:

    Product Owner / Error Handling / Acceptance Testing / Estimation Meeting

    The story:

    The product owner was at the client-side. He used to have an estimation meeting with the team every week. The testers used to test the products on the basis of the acceptance testing, Smoke testing, etc. The error handling was done by the testers at the end and if found were delivered to the developers.
  • Kitt

    The words were:

    Customer / Compatibility / Test Driven Development / Review Meeting

    The story:

    Test Driven Development Review Meeting Customer Compatibility
  • Kateryna

    The words were:

    Agile Coach / Boundary value analyses / Behaviour Driven Development / Tutorial

    The story:

    My Agile Coach use different type of Tutorial. When he gets more practice skills his Behaviour Driven Development looks more improvement. He can use Boundary value analyses in the testing process
  • Vitaliy.arm

    The words were:

    Business Analyst / Boundary value analyses / Testability / SCRUM

    The story:

    Once a business analyst suggested we use scrum for our project, we tried it and we liked it. We also use boundary value analyses, which greatly increased testability.
  • Dmitry Azaryev

    The words were:

    Customer / Install Uninstall Testing / Testability / Community

    The story:

    If your installation is successful on the new system then a Customer and his Community will be definitely happy, so you should perform Install Uninstall Testing and ask your colleagues to improve Testability of your application.
  • Olena Mudrak

    The words were:

    User / Localization / Agile Testing / Community

    The story:

    I'm testing localization used Agile testing to become user be able to play the game with all community.
  • inga

    The words were:

    Tester / System Testing / Agile Testing / Agile Principles

    The story:

    After System Testing had been performed, the Tester was asked to perform Agile Testing based on Agile Principles.
  • inga

    The words were:

    Test Manager / User Experience / Exploratory Testing / Waterfall model

    The story:

    We had a meeting with our Test Manager a new project was presented. Based on our User Experience, he asked us to perform an Exploratory Testing and as soon as this will be reviewed, a Waterfall model will be applied.
  • Karina Maldonado

    The words were:

    Business Analyst / Fuzz Testing / Ad Hoc Testing / Daily Scrum

    The story:

    For our Daily Scrum of tomorrow, our Business Analyst asked us to make a Fuzz Testing for our new client; this is actually the Ad Hoc Testing for this specific client only because we expect to find some failing built-in code assertions, or potential memory leaks.
  • Nicholas Snogren

    The words were:

    Developer / Boundary value analyses / Exploratory Testing / Conference

    The story:

    I am a Developer on my way to speak at a Conference about Exploratory Testing. My topic is Boundary value analyses. On my way to the conference, I was thinking about the meaning of the word meaning. How do you determine if anything has meaning? Well, in a sense, any given word has a certain meaning. For instance, the word dog means the furry animal on all fours who is called mans best friend. However, actions can have meaning as well. I might be following someone very closely, and they could interpret my meaning as sinister. But they could be wrong as well, because in fact, we are both in a very crowded place being jostled about. A lot to think about here.
  • Олександр

    The words were:

    Project Manager / Localization / Crowd Testing / Budget Meeting

    The story:

    The budget meeting provided funds to the project manager to prevent localization of crowd testing
  • Denys Pugachov

    The words were:

    Project Manager / Test Automation / Combinatorial Testing / Daily Scrum

    The story:

    Project Manager insisted on Daily Scrum that Test Automation should be based on Combinatorial Testing.
  • Lesia Myroniuk

    The words were:

    Customer / Happy Path Testing / Code DrivenTesting / Community

    The story:

    We live in the Community where the main person is Customer. He creates new ideas and ask the Community to bring them to life. His goals are payed well. The Customer asked for the most strahge and hard implementation: to copy our Earth and create the same visual world where pople could live. The best programmers and tester are working on it. Every class, method are tested by Code DrivenTesting. For global testing was created Happy Path Testing.
  • Mikhail Odintsov [Exactpr

    The words were:

    Test Analyst / Unit Testing / Context Driven Testing / Planning Meeting

    The story:

    During the agile team Planning Meeting scrum master highlighted that James ( who works as Test Analyst ) should not be focusing on Unit Testing since it's a developers job. At the end of the session scrum master also scheduled another session with those analysts, which are aiming for ISTQB certification. The following session is going to be about basic principles of the Context Driven Testing approach.
  • Silvia

    The words were:

    Test Manager / Portability / Testability / Budget Meeting

    The story:

    The Test Manager brought a project to be tested. We had to test Portability. The Testability was questioned when we had the Budget Meeting.
  • Ashish Vyas

    The words were:

    Test Manager / Security / Agile Testing / Conference

    The story:

    In a testing conference of the most hot topics were Agile Testing. The target audience for this conference were Test Managers from top most companies. Apart from Agile testing, few of the speakers also give some insights on Security of web Applications and demonstrate how to secure website from security breaches.
  • alagupoovizhi

    The words were:

    Test Manager / Domain Testing / Testability / Planning Meeting

    The story:

    As a test manager needs to involve in the Planning Meeting which is having the agenda of what requirements are going to be taken out for testing and deciding the testing timelines , resource availability ,test environment setup and the testing start date and end date. In this meeting while think about the testing estimation , test manager has to think regarding the Testability of the resources and their knowledge on the domain which plays one of the key role while doing the Domain Testing
  • Asia

    The words were:

    Project Manager / Security / Ad Hoc Testing / Agile Principles

    The story:

  • ASHISH VYAS

    The words were:

    Product Owner / Install Uninstall Testing / Agile Testing / Daily Scrum

    The story:

    The product owner of project ask to the testing manager to kindly carried out Install Uninstall testing in to check all possible bugs related to this type of testing and also asked us to have daily scrum and follow all principles of Agile testing.
  • sleezy

    The words were:

    Agile Coach / Cause And Effect Testing / Combinatorial Testing / Conference

    The story:

    An Agile Coach is able to guide team mates to work efficiently and focus on what is important. As part of that role the coach might suggest various ways of testing to the team such as Cause And Effect Testing or Combinatorial Testing for example. The coach may also want to arrange a Conference with other team members if they work remotely.
  • vinodh venkatesan

    The words were:

    User / Error Handling / Agile Testing / Agile Manifesto

    The story:

    The user interface is very good in this application but however the error handling part has to improve. One way to do it by implementing agile testing. Agile manifesto has all the information required to implement.
  • Andrzej

    The words were:

    User / Test Automation / Rapid Testing / Conference

    The story:

    I AM A USER OF THIS BLOG FOR 2 YEARS, I AM INTERESTED IN TEST AUTOMATION AND PERFORMING RAPID TESTING. ONCE I PARTICIPATED IN A CONFERENCE AT WHICH THE ABOVE THEME WERE BEED.
  • Gerstmajer

    The words were:

    Tester / User Experience / Exploratory Testing / Training

    The story:

    As a tester, I would like to improve on and test the user experience by doing exploratory testing and training junior testers to do so, as well.
  • Cardia

    The words were:

    User / System Testing / Ad Hoc Testing / Community

    The story:

    In the game community I am, we are a lot of users. I offered myself to make an Ad Hoc Testing for the new chatroom in our forum. They implemented new features and I really want to test them. I'm following a course of System Testing and Software Testing, so I think I'll be useful!
  • Gheorghe Burlac

    The words were:

    Product Owner / Compliance Testing / Alpha Beta Testing / SCRUM

    The story:

    On scrum meeting, the Product Owner talks about Compliance Testing and Alpha Beta Testing.
  • Liutauras

    The words were:

    Developer / State Transition / Test Driven Development / Planning Meeting

    The story:

    Me and my co-worker Liutauras, have been given a task to test a new software product. First we need to test it using test driven development, which will require a repetition of a very short development cycles. Next we will use state transition testing,in which we will define a number of states that will be required for this test case. And last but not least we will present our plans in the upcoming planning meeting this monday. Besides the QA team, this meeting will include developer Jonas and manager Petras.
  • :)88

    The words were:

    User / State Transition / Data Driven Testing / Conference

    The story:

    On last Conference I have learned that good written User stories are the key to success in preparing tests according to Data Driven Testing approach. If it is possible, State Transition layouts should be included as well.
  • Anitha Balan

    The words were:

    Developer / Performance / Testability / Community

    The story:

    In my community there are developers whos performance are great and there testability are vast in nature.
  • alberto briosso

    The words were:

    Test Manager / Security / Pair Testing / SCRUM

    The story:

    As a Test Manager, you have resposabilities. Security is one of them. Consider Pair Testing teams beforehand could be an advantage, and remember to always use good practices like SCRUM.
  • Abinaya

    The words were:

    Administrator / Compliance Testing / Crowd Testing / eXtreme Programming

    The story:

    The IT team in a company is most important because they help employees resolve issues with their system. The IT Administrator is the first person to be contacted for when we have issues. If the problem is due to us then we sure would be advised by the Administrator to take the Compliance test first. Compliance Testing and Crowd Testing are mostly likely to be know from their point of view. It does not require a knowledge of eXtreme Programming but only a basic understanding is sufficient.
  • balachander

    The words were:

    Administrator / Unit Testing / Model Based Testing / Retrospective Meeting

    The story:

    As a testing i want to test all the administrator role privilege functionalities are covered in unit testing and also want to test model based testing. End of the sprint i have to attend retrospective meeting.
  • Lucas

    The words were:

    Test Analyst / Domain Testing / Alpha Beta Testing / Tutorial

    The story:

    The Test Analyst would like to perform Domain Testing for a product by not only testing himself, but also letting the client to test it (Alpha Beta Testing). However, since the client doesn't know the product well, the tech or product team were requested to write a Tutorial for it.
  • Lucas Santana

    The words were:

    Test Manager / System Testing / Code DrivenTesting / eXtreme Programming

    The story:

    A system has to be built and tested. Both the Tech Lead and the Test Manager wants to use Code DrivenTesting for both System Testing and development under an agile environment, specifically eXtreme Programming methodology. wants to perform a system testing. with a Code DrivenTesting (TDD) under a
  • Svetlana Zaicenco

    The words were:

    Developer / Integration Testing / Rapid Testing / Waterfall model

    The story:

    the developers do integration testing when different parts of software combine togehter. Rapid Testing they perfome means better test strategy, not quicker performance. Waterfall model with it disadvantages still is using in testing.
  • Vinay

    The words were:

    Project Manager / Error Handling / Crowd Testing / Review Meeting

    The story:

    Quality of a product always matter. As a Project manager, Its important to enable crowd testing followed by Review meeting. The output need to be handled for different error handling scenarios.
  • Alhxor

    The words were:

    Test Analyst / Happy Path Testing / Model Based Testing / Agile Manifesto

    The story:

    Yesterday I met a Test Analyst. Last application he worked on was called Happy Path. While performing Happy Path Testing, his team was usually using Model Based Testing, but he did not know what it was at the time. So instead of doing his job he was reciting Agile Manifesto out loud to impress his colleagues.
  • Marina Kts

    The words were:

    Customer / Domain Testing / Pair Testing / Tutorial

    The story:

    A good Customer Tutorial would not usually include references to technical terms, such as Domain Testing or Pair Testing. Please write another Tutorial.
  • Wadafaku Goromenague

    The words were:

    Tester / Integration Testing / Testability / Agile Manifesto

    The story:

    The Agile Manifesto is about the Integration Testing, the Tester and the Testability.
  • Viktoryia

    The words were:

    Test Manager / Portability / Behaviour Driven Development / Training

    The story:

    I am a test manager. Portability is a good feature. Behaviour Driven Development ia a type of testing. Training gives good opportunities for growing.
  • Kartik Saraswat

    The words were:

    Business Analyst / State Transition / Pair Testing / Software Crafsmanship

    The story:

    Software Craftsman ship involves multiple levels of pair testing including state transition to which a business analyst can agree to.
  • Amy

    The words were:

    Scrum Master / System Testing / Context Driven Testing / Agile Principles

    The story:

    There was once a Scrum Master who had a strong belief in the Agile Principles. He wanted to spread the word of these principles and therefore represented these values in his work. He spoke to the testers about them too, and asked them to consider the ways they could use them in their testing. They considered their System Testing practises, and how it could be improved using the principles of agile. After much deliberation they concluded they could use the principles to create the concept of Context Driven Testing, to make their testing efforts more effective. The end.
  • suganyaprem

    The words were:

    Business Analyst / Domain Testing / Acceptance Testing / Review Meeting

    The story:

    QA has another role to play as "Business Analyst" to gather the requirements from the clients and also have an knowledge on Domain Testing for every projects to meet the client satisfaction with the help of Acceptance testing, periodically we have an review meeting to give the better performance
  • suganyaprem

    The words were:

    User / Test Automation / Context Driven Testing / Tutorial

    The story:

  • Galia

    The words were:

    User / Unit Testing / Exploratory Testing / Software Crafsmanship

    The story:

    As the Member of Software Crafsmanship I should assure the quality of applications we produce for end User. We provide it from the lowest level via Unit Testing to the highest level using different techniques, e. g. Exploratory Testing.
  • Serghei Reulet

    The words were:

    Project Manager / Performance / Acceptance Testing / Retrospective Meeting

    The story:

    Our project manager was upset, because we confessed we had't even planned our performance and acceptance testing on the latest retrospective meeting.
  • ZG

    The words were:

    User / Boundary value analyses / Code DrivenTesting / Conference

    The story:

    Here comes the story: user would like to apply boundary value analyses on Code DrivenTesting so he can present it on the upcoming conference
  • Sekhar Uppari

    The words were:

    Customer / Fuzz Testing / Behaviour Driven Development / Review Meeting

    The story:

    Customer is the end user, who is using the application. If customers are happy with your application, then we no need to worry about the competitors. Fuzz Testing means the name of the testing, there is no meaning for the word "Fuzz". Behaviour Driven Development is a kind of development, where the Product managers, developers, and testers will be in sync about the application and its test scenarios. From a testing point of view, we use the CUCUMBER framework for the test case development, which allows testers to follow Behaviour Driven Development. Review meeting is meeting, where this happens in agile methodology. In the Review Meeting generally, the team will discuss and review the user stories development and testing.
  • bell

    The words were:

    Test Analyst / Happy Path Testing / Alpha Beta Testing / Review Meeting

    The story:

    We have tomorrow test analyst and we have to happy path testing this application and then alpha beta testing and lastly we review our meeting
  • Gai

    The words were:

    Product Owner / State Transition / Test Driven Development / Community

    The story:

    The product owner supports test driven development approach as important part of our project. As for testing community, it supports that and in addition underlines that state transition must be used firstly in test design.
  • Hristo Ivanov

    The words were:

    Business Analyst / Test Automation / Ad Hoc Testing / Community

    The story:

    The community needs programs more and more. The business Analyst in any company searches for good solutions for releasing software to become bugles. Test Automation is perfect for this purpose. Ad Hoc Testing is good too but not as good as Test Automation.
  • AmriA

    The words were:

    Test Manager / Compliance Testing / Data Driven Testing / Waterfall model

    The story:

    As a Test Manager, you will need to motivate your team members to become better testers. In doing so, one of the most important aspect is Compliance Testing. For this, testers must validate that the software under test meets the various legal requirements for the domain (e.g. aviation). Data driven testing can be utilized in Compliance testing to validate a variety of input parameters to validate conditions. Waterfall mode is inefficient way to manage software development process because testing is left at the end of the lifecycle. When a problem is found, it is almost too late to redesign the system.
  • Yesterday86

    The words were:

    Customer / Cause And Effect Testing / Combinatorial Testing / Community

    The story:

  • sergey,roskach90@gmail.co

    The words were:

    Customer / Integration Testing / Acceptance Testing / Agile Principles

    The story:

    A customer is looking for company which could do and integration testing and acceptance testing. For customer is really important quality and security of testing and also team which is going to test their software should follow agile principles.
  • Marcela

    The words were:

    Test Analyst / Decision Table Testing / Exploratory Testing / Budget Meeting

    The story:

    As Test Analyst i want to make decision table testing so i can make exploratory testing in order to prepare budget meeting.
  • IvanMilovanov

    The words were:

    Customer / Happy Path Testing / Rapid Testing / SCRUM

    The story:

    SCRUM Rapid Testing Happy Path Testing Customer
  • Paulina

    The words were:

    Business Analyst / Happy Path Testing / Test Driven Development / Software Crafsmanship

    The story:

    Few days ago, Business Analyst talk to me about Happy Path Testing. I told him, that I'm not realy intereseted in that matter, because I should focus on Test Driven Development. He said that it will be great opportunity to develope my Software Craftmanship and other skills, so I decided to take this job.
  • afasfsa

    The words were:

    Test Manager / Fuzz Testing / Testability / Agile Manifesto

    The story:

    Test manager fuzz testing testability agile manifesto
  • 4ndy

    The words were:

    Project Manager / User Experience / Combinatorial Testing / Agile Manifesto

    The story:

    I'm a programming engineer who's working in an important development firm whic works with companies such as banks, electric suppliers, government, and other technological companies. My position is to be the Project Manager in a project to make a banking account management software. I began to work in this company after to have worked as developer during 10 years by making apps for final user, so i have a lot of knowledge in apps designed to give a fine User Experience. At this project, one of my task is to drive a team of software testers, who uses Combinatorial Testing among other testing technics when we must create cases of use. To improve project's performance and quality, we are thinking to introduce Agile Manifesto principles on the entire software development cycle.
  • Akash Mekal

    The words were:

    Agile Coach / Test Automation / Ad Hoc Testing / Conference

    The story:

    In an organization, an experienced Agile Coach should host a Conference once in a quarter and make them realize that not all test suites can be automated, Test Automation is very useful and the ROI is high for Sanity, Smoke and Regression Suite and not for complex changing Functional Testing and Ad Hoc Testing
  • Smith

    The words were:

    Business Analyst / State Transition / Test Driven Development / Conference

    The story:

    in the last conference, we concluded that our business analyst is unable to comprehend Test driven development therefore, he is a subject for State Transition.
  • Ahmed Galal ElMalah

    The words were:

    Project Manager / Unit Testing / Acceptance Testing / Retrospective Meeting

    The story:

    As a Project Manager In order to deliver a good quality project We want to perform Unit Testing and Acceptance Testing As a Project Manager In order to get improved developing our product We want to have Retrospective meeting to share and exchange what can be fixed and improved Given that the project requirement is ready And Planning phase is done When Development started Then Developer needs to perform unit tests Given that the project is ready for QA And the Test activities have to start When the Unit Testing Testing is done And the Integration Testing is done And the Regression Testing is done Then Acceptance Testing should be executed
  • Constantin

    The words were:

    User / System Testing / Alpha Beta Testing / Training

    The story:

    I know that manual testers are more like User that should try everything on application and more then simple User. System Testing is kinda things that all users can do, but they dont know that they are testing somethink. Alpha Beta Testing is a final testing phase. This initial software version is known as the beta version. Training your skills always and anywere to keep changes.
  • Bartosz Kustra

    The words were:

    Developer / System Testing / Pair Testing / eXtreme Programming

    The story:

    When the Developer orders a task of System Testing from an admin extension it requires a Pair Testing environment to run it. Extension called eXtreme Programming will fail.
  • @ummahys

    The words were:

    Product Owner / Compatibility / Context Driven Testing / Waterfall model

    The story:

    As a product owner, i want to be able to compatibility context driven testing with waterfall model.
  • Alexey S (hero)

    The words were:

    Project Manager / Integration Testing / Context Driven Testing / Agile Principles

    The story:

    Once upon a time there has been an agile team. Consisting of a developer, testers, project manager, business analyst, functional analyst and a scrum master. Project Manager said that our highest priority is to satisfy the customer through early and continuous delivery of valuable software. The team decided to develop an app and do some Integration Testing between desktop app and chrome extension. But they forgot to do some Context Driven Testing to ensure that the product will work well within macOS.
  • Chhavi Jain

    The words were:

    Tester / Integration Testing / Acceptance Testing / Tutorial

    The story:

    There are lots of video Tutorial is specially designed for beginners with little or no manual testing skiils. Software Tutorial, must contains the basic skills and concepts of software testing. Tutorial must include the basics of Unit Testing, Integration testing , System testing and Acceptance Testing. For A good tester it is important Tester must know the basic of manual testing. Where Unit tests are most of the time tests by developers only. INTEGRATION TESTING is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing. ACCEPTANCE TESTING is a level of software testing where a system is tested for acceptability. The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery
  • tuben

    The words were:

    Test Analyst / Error Handling / Model Based Testing / Waterfall model

    The story:

    a test analyst will test the error handling using model based testing, the company is using the waterfall model in system development process.
  • Aleksey Morozov

    The words were:

    Customer / Boundary value analyses / Model Based Testing / Community

    The story:

    Our customer send us case to test new features in his application. This application is about taxi. We need to do boundary value analyses for date and time fields. Also, team lead suggested to do model based testing. This application should help our community.
  • RETSETp

    The words were:

    Product Owner / Cause And Effect Testing / Ad Hoc Testing / Software Crafsmanship

    The story:

    As a Product owner I will use Cause and effect testing And Ad hoc testing So test team Software craftmanship increases
  • Pelle Plutt

    The words were:

    Administrator / Integration Testing / Context Driven Testing / Estimation Meeting

    The story:

    Administrators doing Integration Testing has Estimation Meeting for Context Driven Testing.
  • Jasleen Arora

    The words were:

    Tester / Domain Testing / Alpha Beta Testing / Software Crafsmanship

    The story:

    It is important for a tester to have domain testing before alpha beta testing and to earn software craftmanship
  • matbylin

    The words were:

    Developer / Performance / Context Driven Testing / Daily Scrum

    The story:

    Situation is that the Developer have to rewrite the code to improve Performance of the testing module. The result will be checked afrer tomorows Daily Scrum. Whenthe Performance will be improved we start to do Context Driven Testing.
  • anzinto fernandes

    The words were:

    Test Analyst / Test Automation / Combinatorial Testing / Waterfall model

    The story:

    Test Analyst is responsible for testing software before it is delivered to the client. test analyst is the last line of quality control.Test Automation in software testing is using automates software for execution of tests and check the actual outcomes with predicted outcomes. Combinatorial Testing is the testing which is done by combining 2 units so expose faults in interaction between the units. Combinatorial Testing is used to check and test pairwise. SDLC is very important in software development. Waterfall model is such a model which is essential in the early stage of SDLC. in Waterfall model each phase must be completed before entering the next phase.
  • Lorraine

    The words were:

    Test Analyst / User Experience / Data Driven Testing / Review Meeting

    The story:

    The Test Analyst had User Experience in Data Driven Testing which was discussed during the Review Meeting
  • dragos

    The words were:

    User / Component Testing / Context Driven Testing / Tutorial

    The story:

    As a USER i would like to have a TUTORIAL with CONTEXT DRIVEN TESTING about COMPONENT TESTING
  • nurul

    The words were:

    Test Manager / Component Testing / Rapid Testing / Daily Scrum

    The story:

    test manager review a component testing which is using rapid testing in daily scrum methodology
  • pablocze

    The words were:

    Customer / User Experience / Exploratory Testing / Estimation Meeting

    The story:

    after meeting with a customer we had a estimation meeting. Ours scrum master said that in next sprint we have to use only exploratory testing because of time pressure. I was the chosen one because i have user experience in banking sector.
  • Ove Larsson

    The words were:

    Project Manager / Localization / Testability / Training

    The story:

    As a Project Manager I want to make sure that the Localization parts of the app has a high enough level of Testability. It is a good Training opportunity for the Quality Engineer to come up with good testability ideas.
  • Krzysztof

    The words were:

    Developer / Integration Testing / Alpha Beta Testing / Retrospective Meeting

    The story:

    A Developer has issues with his Integration Testing during the Alpha Beta Testing phase, this was brought to a testers attention during a Retrospective Meeting.
  • Markus Wall

    The words were:

    Tester / Performance / Data Driven Testing / Retrospective Meeting

    The story:

    During the retrospective meeting, a tester suggested that we include tracking of performance metrics when running data driven testing, to discern if there are differences depending on the data sets.
  • CoY0t

    The words were:

    User / Error Handling / Alpha Beta Testing / SCRUM

    The story:

    During our daily SCRUM, our User, we have invited to Alpha Beta Testing has an Error Handling
  • Susan

    The words were:

    Project Manager / Unit Testing / Rapid Testing / Community

    The story:

    As a project manager, I can confirm based on information from the testing community that our unit testing meets rapid testing requirements.
  • Jasmine Ahmed

    The words were:

    Business Analyst / Integration Testing / Ad Hoc Testing / Daily Scrum

    The story:

    As a Business Analyst we are preparing for a Integration Testing and Ad Hoc Testing
  • Fahim Ahmed

    The words were:

    Tester / Cause And Effect Testing / Alpha Beta Testing / Planning Meeting

    The story:

    I work at piscolo LLC as a software tester. I love my job. There are many types of testing , most are cause and effect testing, which means the results can be different for every new software you test. Before we do any test, we have to go through alpha beta testing to makesure the software is compatible. One of the best part of my job is planning meeting with my co-workers so we can discuss and help eachother.
  • Patricia Kruger

    The words were:

    Agile Coach / Security / Combinatorial Testing / Daily Scrum

    The story:

    Given I am an Agile Coach When I am in the Daily Scrum Then I have to make sure the team is doing the Combinatorial Testing and Security Testing
  • Ajay Balamurugadas

    The words were:

    Test Manager / Security / Pair Testing / Estimation Meeting

    The story:

    As a test manager, it is of prime importance that I understand the quality requirements of my stakeholders. Most of them overlook security testing compared to functional and usability testing. In my company, we encouraged pair testing to help overcome our blind spots compared to individual testing the entire application. This also helped us get realistic data for our estimation meeting.
  • Geosley Andrades

    The words were:

    Business Analyst / Performance / Alpha Beta Testing / Review Meeting

    The story:

    During Review Meeting Business Analyst identified that Performance of the website was slow during Alpha Beta Testing
  • Tasneem Jagmag

    The words were:

    Scrum Master / Install Uninstall Testing / Agile Testing / Review Meeting

    The story:

    I am doing agile testing for this project. I part of agaile I have to daily report to Scrum Master about the user stories i am working on and the defects which i have reported, tracking and retesting. I will also complete my user story that requires me to do install uninstall testing of this server which is critical part of application. I will then test this story based on test cases which are written and report any defects which i find. In the defects review meeting I will go over the critical and high priority defects and will try to get estimated on when they will be available to QA for retest.
  • Fahri

    The words were:

    Agile Coach / Compliance Testing / Ad Hoc Testing / Agile Manifesto

    The story:

    The Agile Coach request the staff to do the Compliance Testing and Ad Hoc Testing based on the Agile Manifesto
  • Anne

    The words were:

    Project Manager / Domain Testing / Model Based Testing / Agile Principles

    The story:

    As Project Manager I care about Domain Testing. I am planning Model Based Testing. I take care of Agile Principles.
  • Kirill Kudzin

    The words were:

    Administrator / Cause And Effect Testing / Alpha Beta Testing / Budget Meeting

    The story:

    Administrator tells us on the Budget Meeting about Cause And Effect Testing and about Alpha Beta Testing
  • Tom Legg

    The words were:

    Product Owner / Localization / Alpha Beta Testing / Conference

    The story:

    In June of this year, I was alpha beta testing a piece of localization software for a product owner, when I realized I was late for a conference.
  • Tester836

    The words were:

    Developer / Decision Table Testing / Alpha Beta Testing / SCRUM

    The story:

    As a developer I want to see technical documentation, with a complete description of tasks, libraries to use and documentation. Testers should run the application in Alpha Beta Testing and complete the Decision Table Testing. As a project manager I should run the SCRUM every day and write a conclusion for that.
  • Ryan Hill

    The words were:

    Developer / Error Handling / Agile Testing / Retrospective Meeting

    The story:

    A group of Developers had a Retrospective Meeting which involved a discussing regarding Agile Testing and Error Handling
  • Pascaru Radu

    The words were:

    User / Boundary value analyses / Code DrivenTesting / eXtreme Programming

    The story:

    In the application, we verify with the boundary value analyses that the user introduced invalid data for register because he is an arabian. We already did a Code DrivenTesting in order to see if invalid data will impact the source code to fail. It seems that we missed something and we will have to verify it again. In order to do so we tested again the funtionality of of introducing not ASCII format, and the developers did some eXtreme programming to maintain the application and add the funtionality for ASCII characters.
  • Lucian

    The words were:

    Business Analyst / User Experience / Context Driven Testing / Conference

    The story:

  • Eugenie

    The words were:

    Agile Coach / Cause And Effect Testing / Data Driven Testing / eXtreme Programming

    The story:

    This morning at stand-up meeting Agile Coach inform us that we need to provide Cause And Effect Testing for our project as soon as possible because our developers made massive mistakes when made eXtreme Programming. Data Driven Testing is really useful but has defects too.
  • Sarah

    The words were:

    Developer / Integration Testing / Testability / Daily Scrum

    The story:

    It was Monday morning and Daniel, a developer at BigCorp International, was considering what the week had in store for him. He approached the first Daily Scrum of the week with trepidation as he remembered the argument he'd had with the Test Specialist about the Testability of the latest feature: A warning message with no trigger except the client's end solution, which would not be available until Integration Testing started some months from now.
  • Seppo hovi

    The words were:

    Customer / Install Uninstall Testing / Context Driven Testing / SCRUM

    The story:

    With the latest Context Driven Testing project with our largest Customer, we used SCRUM-framework to develop method to replace their existing Install Uninstall Testing method with more modern Agile Testing Method.
  • Valentina Stancu

    The words were:

    Product Owner / Domain Testing / Context Driven Testing / Conference

    The story:

    Given a Product owner attends a testing Conference When Context Driven Testing is presented Then the Domain Testing is understood
  • Memurubu

    The words were:

    Scrum Master / Component Testing / Behaviour Driven Development / Tutorial

    The story:

    I want to be a Scrum Master. I should learn a Component Testing. I need a very useful Tutorial. I do not know what is a Behaviour Driven Development
  • yasmine

    The words were:

    Test Analyst / System Testing / Acceptance Testing / Community

    The story:

    Scenario: assuring acceptance testing has passed during system testing Given test analyst has reviewed the BRS And system is tested When system passes And uploaded in the play store And got verified Then system will be available to the play store community And can be used
  • Boya

    The words were:

    Administrator / Unit Testing / Alpha Beta Testing / Retrospective Meeting

    The story:

    Hello, i'm a administrator and my work is a unit testing web-sites, me with my team do this in alpha beta testing, and i want to Retrospective Meeting.
  • Nikita Melikyan

    The words were:

    Customer / Happy Path Testing / Testability / Conference

    The story:

    The most important part of any company is to have good Customer Support. I wish all testers to have a Happy Path Testing their products. To review the Testability of the offered product we need to held lot's of conferences, which we can do in Conference Hall>
  • Adam Adamov

    The words were:

    Business Analyst / Install Uninstall Testing / Combinatorial Testing / eXtreme Programming

    The story:

    My brother is Business Analyst at IBM. His daily duties are Install Uninstall Testing software. He wants to be expert in Combinatorial Testing and as his pasion is eXtreme Programming skills.
  • Dusan Zekic

    The words were:

    User / Compliance Testing / Ad Hoc Testing / Review Meeting

    The story:

    I am User of OKU application. We often use for Electrical Magnetic Compliance testing diferent wave lengths. If we dont have enough time for test plan, we use Ad Hoc Testing. Every Friday we have Review Meeting, where we discuss about all tasks in different statuses.
  • zranosz

    The words were:

    Business Analyst / Boundary value analyses / Testability / SCRUM

    The story:

    As a Business Analyst in SCRUM project I have to Boundary value analyses to test Testability
  • Gabriel

    The words were:

    Product Owner / Fuzz Testing / Pair Testing / eXtreme Programming

    The story:

    I product owner, fuzz testing and pair testing. Lol eXtreme programming, xd, wtf, lol, i need this to be accepted please
  • silver.veetousme

    The words were:

    Customer / Operational Readiness / Behaviour Driven Development / Training

    The story:

  • Michael

    The words were:

    Tester / Boundary value analyses / Acceptance Testing / Community

    The story:

    Tester Boundary value analyses Acceptance Testing Community
  • Oksana

    The words were:

    Agile Coach / Localization / Model Based Testing / Agile Manifesto

    The story:

    as Agile Coach, I want that testers done Localization testing, when Model Based Testing, when read Agile Manifesto,
  • Aakarsh

    The words were:

    Administrator / Unit Testing / Crowd Testing / Waterfall model

    The story:

    There was an application that needed to be tested using Manual or Automated test cases. The testing team needs to do unit testing after Developer team have given the code or deployed the application for testing as Waterfall model approach was used for software development. The first task in testing was to login into application with Administrator and then after first phase of testing we were doing crowd testing for better effectiveness.
  • Ievgeniia Ganzina

    The words were:

    Business Analyst / Unit Testing / Model Based Testing / Training

    The story:

    Model Based Testing is common used practice nowadays. It recommended to visit related trainings for those, who interested in that approach. It may be helpful for Test Engineer, Business Analyst and even Developers, since it is widely used for Unit Testing.
  • Alexandra

    The words were:

    Product Owner / Security / Crowd Testing / Agile Principles

    The story:

    According product owner requirements in case of security purpose to do crowd testing using Agile Principles
  • Rony

    The words were:

    Scrum Master / Security / Alpha Beta Testing / eXtreme Programming

    The story:

    Every morning during the update meeting the scrum master is telling us to put execute the Alpha Beta Testing. And also we should execute the Security.
  • Paul

    The words were:

    Administrator / Boundary value analyses / Testability / Waterfall model

    The story:

    Administrator is the main user of system. Boundary value analyses is good. Testability is on very high level. Waterfall model doesn't work.
  • Bappi chokhani

    The words were:

    Customer / Performance / Combinatorial Testing / Conference

    The story:

    Currently customer is facing performance issue in there conference call due to combinatorial testing
  • marina

    The words were:

    User / Performance / Rapid Testing / Agile Principles

    The story:

  • AssBlaster

    The words were:

    Customer / Security / Agile Testing / Daily Scrum

    The story:

    Our daily scrum involved our customer's need for additional security during our agile testing phase.
  • patman

    The words were:

    Agile Coach / Component Testing / Code DrivenTesting / Tutorial

    The story:

    Agile Coach Component Testing Code DrivenTesting Tutorial
  • CosminT

    The words were:

    Project Manager / Localization / Testability / Tutorial

    The story:

    How to test: 1. Login as a Project Manager 2. Verify Localization of the Button "Testability" 3. Check the Tutorial"
  • Gaurav Singhai

    The words were:

    Test Manager / Decision Table Testing / Testability / Tutorial

    The story:

    As mentioned in the Tutorial, Test manager asked the tester to check the Testability of functionality with Decision Table Testing as decision table testing is a testing technique used to test system behavior for different input combinations.
  • CriCriToamnaGri

    The words were:

    Customer / Compliance Testing / Agile Testing / Conference

    The story:

    At the Agile Testing Conference we presented the benefits for the Customer of the Compliance Testing.
  • CriCriToamnaGri

    The words were:

    Test Manager / Security / Crowd Testing / Training

    The story:

    The Test Manager decided to attend a Security Training while the rest of us were doing Crowd Testing.
  • Ivo Cunha

    The words were:

    User / Compatibility / Alpha Beta Testing / Tutorial

    The story:

    Given that company "Abc" is finalizing their new product, it is important for the QA team to increase the quality confidence levels. One of the most common ways to do this, is to involve users in the Alpha Beta Testing, as any User can potentially add value by reporting issues on this early stage of the live cycle. Given that it is a new product, special attention should be given to the Tutorial as every single user will go through it on this release. Introducing correctly users to the product and its features impacts retention strongly, which is an important KPI. It is also relevant that, although security, payment and performance should be at the intended level by this stage, that Compatibility checks are completed too. Many users, means many different OSs, devices and formfactors. The targetted market should be fully taken into consideration, alongside the most popular devices at the current date and time. All these factors, will certainly allow a greater quality in the final product, as well as a better outcome as a whole.
  • Snehal Volvoikar

    The words were:

    Tester / Portability / Behaviour Driven Development / SCRUM

    The story:

    Tester is a machine/person who has been asked to test something. For this purpose, he/she should have that particular knowledge. One kind of testing is portability testing in which the software is moved from one environment to another.This can be done iteratively and incrementally. There are many things that can be considered as crucial characteristics for a potential tester. Behaviour Driven Development combines the general techniques and methodologies that are essential to collaborate on software development. Behaviour Driven Development can be considered as an effective technique that every tester should be aware of. Then comes the SCRUM which is the iterative and incremental software development method. Firstly, scrum can be identifies as a framework for project management that mainly focuses on teamwork to achieve the desired goal. Scrum is based on roles, artifacts and ceremonies. Scrum is an efficient way for testing purposes.
  • Mark Flynn

    The words were:

    Product Owner / System Testing / Acceptance Testing / Planning Meeting

    The story:

    Each sprint all the members of the team along with the Product Owner gather together and we all have a sprint Planning Meeting. In this meeting we will go through all the tasks that are required to be developed and tested by the team in the next 2 weeks for a release. Along with the tasks the team also outlines the System Testing and Acceptance Testing criteria that must be met for the sprint.
  • Srushti

    The words were:

    Test Analyst / Happy Path Testing / Acceptance Testing / Software Crafsmanship

    The story:

    Once upon a time there was a test analyst who was working for a big firm. He was very ambitious and dedicated towards his work. He always was ready to accept challenges and face them easily and confidently. One day the senior developer of the firm submitted to him his developed application and told to perform the necessary testing. The application was very challenging to handle. It was difficult to build the test cases so he tried and tried and built one test case. But that wasn't enough. He was very stressed. After a while he calmed himself down and thought of a new testing scenario which is known as happy path testing. In this testing the test cases are created considering positive scenarios. And to his surprise this went perfect for him. Then he applied acceptance testing on it where the negligible minute bugs are accepted. Hence in this way he completed his work and made everyone happy.
  • Daniel Bennett

    The words were:

    Project Manager / State Transition / Pair Testing / Tutorial

    The story:

    The project manager and their colleague were testing a piece of software, they were working together to test the application. The application used the theory of state transition, however the colleague was not fully experienced in this and needed a tutorial (Which is why they were using pair testing). The manager was explaining the theory to the colleague tellin him about the sequential logic and how they can use a table to show what the automation will do based on the situation or state. The project manager knew that clear communication was important for a well developed and efficient team, and did not mind taking the time to tutor the colleague on something that would not only help the QA department as a whole but will also benefit the employee on an individual level. After the tutorial was over the colleague had a much better understanding of state transition and knew that in the future he will be able to use this theory during automation and semiautomation.
  • Durlabh Soni

    The words were:

    Test Analyst / Integration Testing / Ad Hoc Testing / Review Meeting

    The story:

    One of the major task of test analyst is to perform integration testing, and if required to perform Ad Hoc Testing, these tasks could be put forward during review meeting
  • Diksha

    The words were:

    Test Manager / Performance / Pair Testing / Agile Principles

    The story:

    The companys test manager is a capable person with excellent analytical skills and has been awarded with the best performer of the year award based on his annual performance.But now since the company is expecting to undertake more projects he has to pair up with new empolyess for the pair testing task.So this would indeed satistfy the agile principles responsible for companys betterment.
  • Mohit

    The words were:

    User / Integration Testing / Alpha Beta Testing / Community

    The story:

    After the unit testing is done we move on to integration testing wherein all the units are integrated and tested to check whether they work together as expected.After integration testing, we perform system testing and finally we perform user acceptance testing. The user acceptance testing involves the alpha beta testing. Alpha testing is carried out in a lab environment and usually the testers are internal employees of the organization.Beta testing comes after alpha testing wherein versions of the software, known as beta versions are released to a community of testers so that further testing can ensure the product has few faults or bugs.
  • Poonam Jamuni

    The words were:

    Customer / Compatibility / Alpha Beta Testing / Conference

    The story:

    A customer purchased a product that was according to its requirements. Later on, the customer had more requirement . So the company has a conference meeting regarding the requirements. After the requirements were satisfied it was given to the employees and the user for alpha Beta testing. Further on the compatibility of the product was tested.
  • vinayak

    The words were:

    Developer / Compliance Testing / Data Driven Testing / Conference

    The story:

    Project of developing malaria detection GUI . The code written by Developer and as per the Developer the application is ready for testing the compliance testing was done and the result was as per the requirement but in data driven testing the accuracy was 68% as per the client requirement the accuracy has to be above 75% so the developer had to make some changes in the code and after changes the testing was conducted in the Data Driven testing the accuracy was 78% so after the completion of test in the conference meeting we discussed about the methods we approach for the required output to achieve .
  • plm

    The words were:

    Administrator / Integration Testing / Exploratory Testing / Conference

    The story:

    An Administrator was walking down the street, on a beautiful Saturday morning. Suddenly, he was invited to a Conference for Gay Pets Owerns, as he had a gay pet penguin. That sounded pretty interesting as he instantly saw the Exploratory Testing potential to which he could expose his gay penguin at, even if he was only an expert in Integration Testing.
  • RIch

    The words were:

    Developer / Component Testing / Rapid Testing / Tutorial

    The story:

    you are a developer and you are implementing a tutorial site, and you are required to do both component testing and rapid testing.
  • Rafaela

    The words were:

    Customer / Test Automation / Ad Hoc Testing / Retrospective Meeting

    The story:

    The customer wanted to do the ad hoc testing to his product, so we decided at the retrospective meeting that we should do the test automation before
  • Maryia

    The words were:

    Business Analyst / Portability / Rapid Testing / Agile Manifesto

    The story:

    Once a Business Analyst decided to become a QA engineer. He read a lot of books, forums and, finally, he finishe training courses and was hired for a job as a QA engineer in a very popular start-up company. The first task on his project was to check Portability of the device they were given and, since it's a start-up company, it should be a rapid testing . He executed his testing really fast and even was able to help his new colleague. At the end of the day the team had a stand up call and he was told, that this team supports Agile Manifesto. It was something new for him, because he has never heard anything about Agile, so he found some sources and read about the agile manifesto in the evening and he loved this practice.
  • Sohan Sabnis

    The words were:

    Scrum Master / State Transition / Alpha Beta Testing / Budget Meeting

    The story:

    Once upon a time there a organization got a mega project since its inception and the organization was very happy to do so and upgrade their selves as one of the major startups.The project was to develop an ecommerce website for a multinational corporation dealing in the field of clothing.The team was selected here in the organization and it comprised of 12 people.With all said and done there was a Budget Meeting held to discuss the man power and resources and time and cost involved to create a big time project.The project leader was then named also as the Scrum Master and the planning began and the plan was drawn how to do the state transition to various levels and the work was divided and the go ahead was given.Weekly scrum meetings were held and the Scrum Master ensured all the things are in place.The project had its transitions done from design to coding phase and the coding was going well until two members of the core team fell ill and it poised the project completion in a very critical stage as the deadlines were approaching.The Scrum Master had then taken it upon himself to carry the burden of the same and the workforce began working like horses to ensure the perfect and smooth workflow.After a few months the coding was complete and the product was ready for initial testing and the testing was done and ready for acceptance testing.The team had never felt such pressure over them to finish a project before but this was a high profile and immense money benefits and customer satisfaction involved.The acceptance testing was through and there were a few discrepancies observed but the team managed to clear them off and now headed to the Alpha Beta Testing. The Alpha Beta Testing was also cleared and the project was successfully handed over to the customer and it was a huge success for the team despite their two major team members missing due to serious illness.The customers were much excited with the product received and gave a ton of credit to the Project team and the development and testing team also to mention the two members of the team who were sick.The customers offered a big helping partnership hand to this organization and ensured more business is done in the months to come.This made the team very happy and satisfied with what they had done and they enjoyed its rewards in terms of money and recognition.The Scrum Master then congratulated all the team and organization in the annual function and appreciated everyone for the same.The same was welcomed by a loud applaud. Moral of the story : Never give up on obstacles faced and take every problem as an adventure
  • Oleksandr Petukhov

    The words were:

    Scrum Master / Boundary value analyses / Code DrivenTesting / Daily Scrum

    The story:

    Business Analyst, Localization, Ad Hoc Testing, Tutorial, Scrum Master Boundary value analyses Code DrivenTesting Daily Scrum
  • Manal

    The words were:

    Test Manager / Test Automation / Test Driven Development / Budget Meeting

    The story:

    the test manager has to arrange a budget meeting between test automation team and test driven development team at the first week to discuss Budget required
  • Daniel Pavaloaia

    The words were:

    Scrum Master / Test Automation / Ad Hoc Testing / Agile Manifesto

    The story:

    The Scrum Master came late during today meeting, once he came he reminded us the Agile Manifesto. Paul needed his help as there were some issues from a previous project and no time to finish the Ad Hoc Testing. The Test Automation is not looking well, we still need an experienced tester in our team.
  • Catalin Tanasie

    The words were:

    Administrator / Integration Testing / Agile Testing / Daily Scrum

    The story:

    We should talk today at our daily scrum about the new product. We need to do the Agile testing as soon as possible. Also, we need to make an integration testing between the old app and the new app. Also, i need to ask our administrator to give us acces to database.
  • Pooja

    The words were:

    Developer / Performance / Model Based Testing / Waterfall model

    The story:

    Software Developer develops the software or the module. performance- It is a process of performing a task with application of knowledge, skills and ability in the work place. An effective performance is determined by achevement skills and competency of the performer. model based testing: It is an application of model based design for designing and optionally also executing artifacts. waterfall model: It was the first process model to be introduced. It is very simple to understand and use. The waterfall model has following phases: a. requirements b. system design c. implementation d. Integration and testing e. Deployment of system f. Maintainence The next phase is started in waterfall model only after the defined set of goals are achieved for previous phase and it is signed off, so the name waterfall model.
  • Gayle Diniz

    The words were:

    Developer / State Transition / Pair Testing / Training

    The story:

    I am a developer and I have been well trained by the company I am working with. I work with pair testing and state transition
  • Anca Cacencu

    The words were:

    Project Manager / Decision Table Testing / Pair Testing / Training

    The story:

    Today our Project Manager came up with a few suggestions regarding the Training program. After our sprint planning session, is has been decided that John and Jimmy will perform Pair Testing and a 2 more other members of the team will be assigned on Decision Table Testing.
  • Dhameliya Khushali M

    The words were:

    Product Owner / Localization / Testability / Waterfall model

    The story:

    We had a Planning Meeting yesterday with the Product Owner and he rose two issues. The first is that a lot of Unit Testing is done by developers, but it is not transparent to the agile testers and product owners. The second was that the Testability is not considered in the planning meetings.Tester doing localization testing using the waterfall model.
  • Francis

    The words were:

    Customer / Unit Testing / Context Driven Testing / Planning Meeting

    The story:

    You work as a tester for a major financial company. Today a customer approached you and asked you to report on what Unit Testing you have provided for a product your company supplies to them. You explain that while you have 100% code coverage in the application with your unit tests that the product may still not be able to cope in live and suggest that you do some Context Driven Testing to ensure that the product will work well within the new environment. After some consideration and explanation on your part, the customer agrees to the idea and suggests that you present this in a Planning Meeting with the project manager and higher ups within the customer's company.
  • test

    The words were:

    User / Localization / Model Based Testing / Conference

    The story:

  • dharmendra

    The words were:

    Business Analyst / Localization / Rapid Testing / Estimation Meeting

    The story:

    today we had a meeting with QA Estimation meeting with Business Analyst with focus on localization of data and steps to followed for rapid testing
  • Sebastian W

    The words were:

    Developer / Integration Testing / Agile Testing / Training

    The story:

    While the developer feels comfortable doing Integration Testing, he lacks the Training and experience to do Agile Testing.
  • Oleksandra Zubal

    The words were:

    Product Owner / Error Handling / Ad Hoc Testing / Agile Manifesto

    The story:

    All junior software testers usually start with taking some software testing course, whether offline or online. They're taught how to do ad hoc testing as part of their course agenda. This can help them in their career advancement. In the future, they can even learn how to be Product Owners! The majority of them will work in software development companies creating products using Agile approaches. Therefore, they should know Agile Manifesto by heart in order to apply it in practice. They should also have necessary skills in error handling testing and monitor the application after incorrect input. Being a software tester can be challenging. But it's fun too.
  • l1venotonev1l

    The words were:

    Administrator / Boundary value analyses / Context Driven Testing / Conference

    The story:

    On Conference Administrator talks about Boundary value analyses in Context Driven Testing
  • NoemiMG

    The words were:

    Business Analyst / Decision Table Testing / Rapid Testing / Estimation Meeting

    The story:

    Yesterday I met the Business Analyst, he was a good person, so we were talking about the project advance in the estimation meeting, and he wanted to make a rapid testing about some of the functions. Everything worked perfectly. One of the things that helped me valid possible inputs and outputs of the user was the Decision Table Testing we made.
  • Rifatra Rathod

    The words were:

    Administrator / Operational Readiness / Test Driven Development / Retrospective Meeting

    The story:

    In the Retrospective Meeting decision was taken to use Test Driven Development and Administrator to demonstrate Operational Readiness
  • Rifatra Rathod

    The words were:

    Scrum Master / Performance / Exploratory Testing / Retrospective Meeting

    The story:

    In the morning standup the Scrum Master requested the Performance team to share the results of the test last night and asked the functional testers to include Exploratory Testing in the process and in the afternoon a Retrospective Meeting is scheduled for the current sprint
  • rocio

    The words were:

    Project Manager / Operational Readiness / Exploratory Testing / Training

    The story:

    The Project Manager asked me if I could do a Exploratory Testing while I was Training with the new interns, he told me it was only Operational Readiness review of the system.
  • Danica Gjorgjevska

    The words were:

    Customer / Operational Readiness / Pair Testing / Budget Meeting

    The story:

    The customer insists on having the application in operational readiness state before the end of the month. Pair Testing is mandatory. Any other testing is optional. During the budget meeting that was held on Monday it was decided that due to budget constrains, other than pair testing, only small scope of regression testing will be conducted.
  • Maria Eugenia Belhot

    The words were:

    Test Manager / System Testing / Combinatorial Testing / Planning Meeting

    The story:

    I´m the Test Manager of a System Testing that has Combinatorial Testing and we are planning Meeting soon in order to exchange information.
  • Stefanel Dragomir

    The words were:

    Developer / Integration Testing / Acceptance Testing / SCRUM

    The story:

    In today's SCRUM, the developer had some questions about who is performing the integration testing, he was concerned that there are some junior testers doing these important tests and there might be risks during the acceptance testing.
  • smogilevsky

    The words were:

    Customer / Security / Model Based Testing / eXtreme Programming

    The story:

    As a result of customer testing we got a report saying that out login for has a security breach. This breach was somehow not found by our model based testing and also missed by our team afterwards. We have a thought that this happaned because of the eXtreme Programming approach that we are trying to use. Seems like our team is not yet ready for it. Need to think about it later.
  • GiovanniSpagnolo

    The words were:

    Product Owner / Security / Ad Hoc Testing / Agile Principles

    The story:

    Today the Product Owner found a Security issue, for this bug, following the Agile Principles we created an Ad Hoc Testing suite only for this issue
  • Nelli

    The words were:

    Test Manager / Domain Testing / Pair Testing / Community

    The story:

    Test Manager helps the local community with doing some domain testing and not being busy with au pair testing abroad.
  • Vladimir Bud

    The words were:

    Test Analyst / Fuzz Testing / Combinatorial Testing / Community

    The story:

    A job of the Sotware Test Analyst is to ensure that the software that is released meets the specified requirements and does not have critical bugs. Test Analysts use Fuzz Testing (testing on unexpected/wrong data), Combinatorial Testing (testing on all combinations of input) are numerous other software quality assurance techniques aknowledged by the Community to test the software.
  • Euggenni

    The words were:

    Developer / Unit Testing / Acceptance Testing / Community

    The story:

    The Developer is responsible for creating Unit Testing. They are necessary for Acceptance Testing. He is assisted in this motley Community.
  • DmitryUtkin(Ahinedark)

    The words were:

    Test Analyst / Test Automation / Exploratory Testing / Software Crafsmanship

    The story:

    As a Test Analyst, i have to analyze the work done to Test Automation. And my Software Crafsmanship skill allows me to apply Exploratory Testing.
  • Tapani

    The words were:

    Agile Coach / Boundary value analyses / Combinatorial Testing / Planning Meeting

    The story:

    During a Planning Meeting our Agile Coach shared his knowledge about Combinatorial Testing and Boundary value analyses.
  • Johan Rönnlund

    The words were:

    Product Owner / Boundary value analyses / Ad Hoc Testing / Conference

    The story:

    Even as a Product Owner it is very good to know the basics of testing. Like if you want to rush a very important feature, like a new field on your web site, you should never push your team to skip testing. But Ad Hoc Testing might suffice here (depending on the risks involved), and since they are undocumented and only meant to be run once, they can be done quickly, but still be very good if you have experienced testers, that do not forget to include all basic software testing techniques like Boundary value analyses. Knowing basic stuff about testing, is important even for you, allowing you to better make the correct decisions, and turning your products into success stories. Perhaps giving you the success story to talk about on your next big Conference.
  • FilipPp

    The words were:

    Agile Coach / Test Automation / Combinatorial Testing / Software Crafsmanship

    The story:

    Agile Coach is trained as Test Automation. Combinatorial Testing is like Software Craftsmanship.
  • dijumatoce

    The words were:

    Developer / Error Handling / Rapid Testing / Estimation Meeting

    The story:

    As a developer i want to be able to provide an error handling of the application logs while doing a rapid testing in order to provide a metric on the estimation meeting
  • Malwina

    The words were:

    Scrum Master / Test Automation / Test Driven Development / Daily Scrum

    The story:

    On a Daily Scrum meeting our Scrum Master told us, he would like to understand more technical aspects of our work. He asked us QA and developers team to show him an example of Test Automation tools and a little explanation of how Test Driven Development really works.
  • Billy Ngamilo

    The words were:

    Developer / Operational Readiness / Acceptance Testing / Retrospective Meeting

    The story:

    As a developer I need to create a new account. Operational readiness in the project ensures the working environment is ready to support and accept changes from the project. Acceptance testing is testing the system to evaluate if it conforms to business requirements and whether it can be accepted. Retrospective meeting is a sprint meeting in agile Scrum where team members reflect on the past Sprint and check for three main things: What went well,what di not and what could be done to improve for future sprints.
  • Gizela

    The words were:

    Customer / Fuzz Testing / Acceptance Testing / Software Crafsmanship

    The story:

    As Customer I want to make sure that Fuzz Testing and Acceptance Testing were covered in Software Crafsmanship
  • Billy Ngamilo

    The words were:

    Customer / Unit Testing / Testability / Community

    The story:

    As a Customer I want to create new account. Unit testing will be done by the developers. Acceptance criteria is necessary for testability of any user story. Selenium Webdriver has a large user support community.
  • subofer

    The words were:

    Business Analyst / Portability / Crowd Testing / Waterfall model

    The story:

    I, a Business Analyst need to test the new idea, of phone number Portability, the idea is make a Crowd Testing arena, with hundred of phones, and make it using the Waterfall model.
  • dortqa

    The words were:

    Test Manager / System Testing / Exploratory Testing / Agile Manifesto

    The story:

    As a Test Manager I want to do System Testing/ Method used will be Exploratory Testing according to Agile Manifesto.
  • JulyaBoldyreva

    The words were:

    Test Analyst / State Transition / Rapid Testing / Training

    The story:

    Test Analyst tested State Transition of Big System. His not smart pupil asked: "It is Rapid Testing, isn't it?" Test Analyst looked at him strictly and said: "Your Training is not over. You shouldn't know my methods of testing" Was it really secret method? Of course, wasn't. But floor hadn't washed yet.
  • Anu Chandru

    The words were:

    Tester / Domain Testing / Testability / Agile Manifesto

    The story:

    A person who always follow the rules and regulations of the agile manifesto and is capable of domain testing skills and put in all his innovative testability skills to reach his goal supposed to be a good tester.
  • Marko

    The words were:

    Customer / System Testing / Behaviour Driven Development / Training

    The story:

    Customer need System Testing for his application. Our development team need Training for this because Behaviour Driven Development is deficient.
  • Vika Churakova

    The words were:

    Product Owner / User Experience / Testability / SCRUM

    The story:

  • Laurentiu S

    The words were:

    Developer / Domain Testing / Pair Testing / Daily Scrum

    The story:

    Developer do a Domain Testing and Pair Testing using Daily Scrum
  • Rory S

    The words were:

    Test Analyst / Component Testing / Ad Hoc Testing / Community

    The story:

    As a Test Analyst I would like to use Ad Hoc Testing to give me an early impression of the software. This will give me quick insights in my boundaries and scope of what I should be testing. Afterwards I will gain more information by working together with the Community; be it a Developer team or other engineers. If the software is complex enough, we could take a look at Component Testing. By defining the borders on what the Community tests and what I can test, I can create scenarios based on both my Ad Hoc Testing and their tests. This way we can assure what is automatically tested and what we can exploratory test.
  • Vangelis

    The words were:

    Customer / Error Handling / Data Driven Testing / Estimation Meeting

    The story:

    The Estimation Meeting with the Customer is for tomorrow. So, we should have the Data Driven Testing and any Error Handling until the end of the day.
  • Lena_d

    The words were:

    Product Owner / Security / Rapid Testing / Budget Meeting

    The story:

    My day started with coffee and Budger Meeting. I did Rapid Testing. The Product Owner came unexpectedly. We discussed important issues. From the conversation, I realized that it is very important security product.
  • Siarhei_Kub

    The words were:

    Tester / System Testing / Crowd Testing / Agile Principles

    The story:

    One day Tester came to workplace to start Monkey Testing. He must do System Testing and Crowd Testing, but he didn't like both. On the wall hung a paper with written Agile Principles. The paper was crossed out because Tester liked Waterfall model.
  • fred steenbergen

    The words were:

    Scrum Master / System Testing / Exploratory Testing / Conference

    The story:

    As a Scrum Master I will have to make sure that the proper amount of System Testing has been performed so it is useful to start with Exploratory Testing after which we have a conference with our stakeholders to come up with the proper next steps
  • batsmu@gmail.com

    The words were:

    Product Owner / Test Automation / Alpha Beta Testing / Daily Scrum

    The story:

    On the daily scrum product owner fecit asked test automation after alpha beta testing.
  • Krasimir Matev

    The words were:

    Product Owner / Unit Testing / Testability / Planning Meeting

    The story:

    We had a Planning Meeting yesterday with the Product Owner and he rose two issues. The first is that a lot of Unit Testing is done by developers, but it is not transparent to the agile testers and product owners. The second was that the Testability is not considered in the planning meetings. "How can you test the remote functionality when the user stories which deals with the connections is left at the second phase?" - he asked.
  • Haz

    The words were:

    Project Manager / Fuzz Testing / Model Based Testing / Agile Manifesto

    The story:

    As a project manager, we need to do a model based testing as per our Agile manifesto instead of Fuzz Testing
  • bleh

    The words were:

    / / /

    The story:

  • Pudding

    The words were:

    User / Integration Testing / Rapid Testing / Retrospective Meeting

    The story:

    A User would like to perform Integration Testing. She doesn't have much time, so she elected to perform Rapid Testing by holding a Retrospective Meeting with her coworkers.
  • Geoffroy

    The words were:

    Project Manager / Operational Readiness / Context Driven Testing / Budget Meeting

    The story:

    The Project Manager ended up in the wrong meeting: he tried discussing the impact that the introduction of Context Driven Testing in the company would have on our Operational Readiness during a Budget Meeting.
  • Vlad Bobes

    The words were:

    Product Owner / Fuzz Testing / Test Driven Development / Tutorial

    The story:

    The Product Owner made a tutorial of fuzz testing. Testers have to make a test driven development.
  • Ilya Sintsov

    The words were:

    Tester / Compliance Testing / Combinatorial Testing / SCRUM

    The story:

    Once a junior tester came to a company on interview. He was speaking with CEO in a conference room. And CEO asks - 'Do you know what is Compliance Testing?. And tester says - 'No idea'. And than CEO asks - 'Okay, do you know what is Combinatorial Testing?'. And tester says - 'No, no idea'. And than CEO asks - 'Maybe you know anything about SCRUM?'. And tester replied - 'Still nothing'. CEO gave him a job offer because he was CEO of OnliQAcourses.com and they needed a totally dumb person.
  • Гончар Ирина

    The words were:

    Tester / Error Handling / Combinatorial Testing / Tutorial

    The story:

    I`m junior tester. After readed user tutorial I`m doing Combinatorial Testing. If i finding bugs i incloud their in Jira. Then doing Error Handling and write report
  • Ognjen Ninic

    The words were:

    Customer / Security / Combinatorial Testing / Agile Manifesto

    The story:

    Customer wants to improve Security of the site. Using Combinatorial Testing they found bugs. Agile Manifesto was their biggest strength in the process.
  • Roberto de Toledo

    The words were:

    User / Error Handling / Model Based Testing / Tutorial

    The story:

    As a User I need a Tutorial to perform Model Based Testing in order to deal with Error Handling.
  • Dmytro Nahorniak

    The words were:

    Administrator / Operational Readiness / Code DrivenTesting / Conference

    The story:

    After the Conference dedicated to Code DrivenTesting our Administrator show Operational Readiness
  • Erika Cebanauskė

    The words were:

    Scrum Master / System Testing / Alpha Beta Testing / Planning Meeting

    The story:

    Scrum master asked a tester to do System testing and give it to a client which should do Alpha Beta Testing. All testing process was discussed in Planing Meeting.
  • Riyaz Uddin

    The words were:

    Test Manager / Portability / Exploratory Testing / Daily Scrum

    The story:

    The person who will co-ordinate and monitor the tester is Test Manager. Portability is something which is transferable or portable. Exploratory testing is less planning and more testing of a task. Daily scrum is a part of agile process. There have four stage of this process. 1) Daily Scrum 2) Sprint planning meeting 3) Sprint Review Meeting 4) Retrospective
  • Kibblator

    The words were:

    Test Manager / Localization / Agile Testing / Conference

    The story:

    A Test Manager attended an Agile Testing Conference to talk about the way that they had split out their Localization project into smaller chunks to allow continuous testing and integration.
  • Olaf

    The words were:

    Tester / Domain Testing / Pair Testing / eXtreme Programming

    The story:

    A Tester and a developer were performing eXtreme Programming as an exercise in Pair Testing in Domain Testing.
  • João Carvalho

    The words were:

    Tester / Decision Table Testing / Rapid Testing / Agile Manifesto

    The story:

    Tester - Use-case analysis, design of test scenarios, system verification and compliance of test cases Decision Table Testing , test diferent scenarios acording with the conditions, expect some action/results Rapid Testing - Verify if the applications works, and check the mandatory fields Agile Manifesto - We have two weeks to develope and test this new part of the system
  • Jasmina N

    The words were:

    Test Analyst / Happy Path Testing / Test Driven Development / Estimation Meeting

    The story:

    At the Estimation Meeting Test Analyst has to provide information about Happy Path Testing and to suggest what will be included into Test driven Development.
  • zavo

    The words were:

    Scrum Master / Error Handling / Agile Testing / Agile Principles

    The story:

    Scrum Master must ensure that the rest of the team can accomplish given tasks during the sprint. he is in charge of error handling, helping people to move over obstacles. Agile testing means that the quality assurance team has to create a strategy to cover all features and parts of the product in the given limited time and deliver best quality possible. Agile principles are important for every member of the team and the scrum master has to make sure they are respected and can help other team members to stick to the plan. There are steps like planning, poker planning, retrospective, daily stand ups and others which help the team guide trough the successful end of a sprint.
  • Ahxejib

    The words were:

    Administrator / Integration Testing / Pair Testing / Agile Principles

    The story:

    In order to be able to perform integration testing, you will need Administrator permissions. Login and password can be found in the documentation of corresponding integration. Pair testing (test engineer with developer) is highly recommended in this activity. According to Agile Principles, feature should be deliver after all phases are completed: development, testing by developer, pair testing, testing, testing at Stage environment, bug fixing, testing after fixes and testing after release (bugfix and repeat testing cycle if needed).
  • Huib Schoots

    The words were:

    Administrator / Happy Path Testing / Behaviour Driven Development / Software Crafsmanship

    The story:

    In this project we value software craftmanship, therefore we encourage out teams to use behaviour driven development and specification by example. All software developed will be tested by the developers first. They have to do happy path testing and negative testing as a minimum. Since we think testers are an essential part of the team we give all team members administrator rights in both the development and test environment.
  • Santhosh Tuppad

    The words were:

    Tester / System Testing / Alpha Beta Testing / Community

    The story:

    As a passionate software tester, I would love to test software better and also focus on my learning consistently to perform better. And one of the source of my test learning happens through the testing community where we argue, debate, discuss for improving our craft and these are some of the qualities of being a context-driven tester. System testing and alpha beta testing, I am not sure about how I can explain these because it can vary based on the context, project, stakeholders, and key members of the project. Nevertheless, I believe that my testing covers these aspects very well and these can be the subset of my testing activity. Last, but not least; this webpage or challenge description contains a typo "bellow" instead of "below".
  • Bogdan Bivolaru

    The words were:

    Developer / Compatibility / Exploratory Testing / Agile Manifesto

    The story:

    In one of my projects, was working with one other developer. We were always late to perform the required changes and the customer started complaining: then we discovered the Agile process. The company was sceptic at first, but then we brought out the Agile Manifesto and the managers saw others have switched to this process before and began to trust us more and more. Most of all the company started to like the fact that we kept the customer in the loop. During our DEMO meetings we started to show what test cases we have performed - most were regression and compatibility testing at first. But then as the application grew we also started to automate most of the regression and we had more time to perform exploratory testing. And that is how the customer was amazed that we were able to find the most weird bugs and their team started to become more and more productive with our software.
  • Mark

    The words were:

    Business Analyst / Decision Table Testing / Crowd Testing / Retrospective Meeting

    The story:

    once upone a time one Business Analyst was playing guitar. He made up song and call it "Decision Table Testing". Here its lyrics: My baby left me My baby left me for crowd testing My baby left me But Iwill chase her I will hunt her And I will find her on Retrospective meeting Wher we belong
  • Justine Palmier

    The words were:

    User / System Testing / Acceptance Testing / SCRUM

    The story:

    The tester has to test by performing actions/cases from a user's perceptive in order to allow the users to enjoy using the product without having any issues. Before testing features and functionalities of a product (online casino), it is important to perform system testing in order to confirm that the site loads fine on a test environment within a particular browser and OS across all platforms. After that testing level, the acceptance testing can be performed to verify if all the functionalities are working and identify bugs if any. During this testing procedure, the tester needs to verify that the functionalities, like "login" fit the user's needs as expected without having any defects and problems. All the bugs that are found need to be reported and JIRA tickets must be created in order to be included in future projects and sprints for fixing them. This development process is part of SCRUM framework. During the SRUM stand up meetings, a decision will be made to decide what to include in the sprint within a deadline to release.
  • Sezel Ismail

    The words were:

    Tester / System Testing / Agile Testing / Retrospective Meeting

    The story:

    The Tester is exequting the System Testing and Agile Testing and have to get Estimation Meeting every 2 weeks.
  • MartaE

    The words were:

    Developer / Performance / Behaviour Driven Development / SCRUM

    The story:

    The Developer would like to add value to the Performance of the new module. She would like to achieve this goal by harnessing Behaviour Driven Development based on user stories. The development of the new software will be performed in a SCRUM type of environment with numerous incrementations at short intervals of time.
  • lorange

    The words were:

    Administrator / Localization / Acceptance Testing / SCRUM

    The story:

    As an Administrator I would like to have the rule if Localization isdefined then Acceptance Testing needs to be started using SCRUM
  • Adam Andersson

    The words were:

    Project Manager / Domain Testing / Rapid Testing / SCRUM

    The story:

    A Project Manager who leads a team of four really skilled exploratory testers who´ve been schooled and mentored by James Bach and Michael Bolton, have had a really sucessful sprint by the help of their good scrum master and their daily stand up meetings. Lets not forget about John who´ve done an excellent job with the Domain Testing with his boundaries values and his equivalence classes equivalence class. Rapid testing isn´t about testing fast, Scrumboard.
  • Vali Vizuroiu

    The words were:

    Product Owner / Compliance Testing / Acceptance Testing / Tutorial

    The story:

    The Product Owner requires Compliance Testing. Acceptance Testing can also be applied after following their Tutorial.
  • Jantien

    The words were:

    User / Test Automation / Test Driven Development / Budget Meeting

    The story:

  • Filip George

    The words were:

    Developer / Security / Alpha Beta Testing / Planning Meeting

    The story:

    During the Planning Meeting a Developer suggested that besides the Security testing we should perform Alpha Beta Testing again during this sprint.
  • Dusan Kuvalja

    The words were:

    Agile Coach / Domain Testing / Context Driven Testing / SCRUM

    The story:

    Agile Coach give us a training about SCRUM since we need to do some Domain Testing by approaching it by Context Driven Testing.
  • Claudiu Arbanas

    The words were:

    Scrum Master / Component Testing / Rapid Testing / Community

    The story:

    The Rapid Testing Community has a old Scrum Master who's now doing Component Testing.
  • Djek Asgardov

    The words were:

    Agile Coach / User Experience / Rapid Testing / Review Meeting

    The story:

    Good day. I'm Agile Coach. Every day we're trying to get more User Experience for better Rapid Testing. For that reason we organize Review Meeting with our customers.
  • Tomasz Smiatacz

    The words were:

    Test Analyst / Domain Testing / Model Based Testing / Planning Meeting

    The story:

    Test Analyst is a person responsible for Domain Testing, especially Model Based Testing, as estabilished on Planning Meeting.
  • Alex Marchis

    The words were:

    Product Owner / Unit Testing / Agile Testing / Budget Meeting

    The story:

  • scarabeus

    The words were:

    Developer / State Transition / Context Driven Testing / Tutorial

    The story:

    Once upon a time there has been an agile team. Consisting of a DEVELOPER, testers, project manager, business analyst, functional analyst and a scrum master. The developer decided to create a TUTORIAL on how to create a STATE TRANSITION diagram. Once he was done, a tester approached him, asking him about CONTEXT DRIVEN TESTING - what is it? He had no idea, so he started googling...
  • SamAnt

    The words were:

    Agile Coach / Fuzz Testing / Model Based Testing / Software Crafsmanship

    The story:

    Agile Coach teaches his pupils Fuzz Testing and Model Based Testing. And all this creates a big and solid Sofrware Crafsmanship.
  • Stanasel Alin

    The words were:

    Developer / Integration Testing / Test Driven Development / Budget Meeting

    The story:

  • Kirill Kopov

    The words were:

    Project Manager / Integration Testing / Combinatorial Testing / Estimation Meeting

    The story:

    Our Project Manager established weekly Estimation Meeting to improve Integration Testing and Combinatorial Testing estimations
  • Alexey Kozlovsky

    The words were:

    Administrator / State Transition / Model Based Testing / Estimation Meeting

    The story:

  • Alice Moretti

    The words were:

    User / Install Uninstall Testing / Data Driven Testing / Tutorial

    The story:

    Testing First Time User Experience involves testing tutorials as well as Install Uninstall Testing. Additionally, in order to retain such first time user it is advised to also run Data Driven testing to make sure that Data retention is working.
  • Edwin

    The words were:

    Product Owner / System Testing / Context Driven Testing / Community

    The story:

    We are preparing for system testing. Waiting for product owner to give green light. Next steps is context driven testing. We will see what community think about it.
  • Michał Szczelina

    The words were:

    Developer / Localization / Agile Testing / Conference

    The story:

    As a Developer I want to take part in Conference about Agile Testing in some Localization
  • Sairaj Chopdekar

    The words were:

    Test Manager / State Transition / Model Based Testing / Tutorial

    The story:

    There was a IT firm named SAM IT services there were many services provided by this firm like cloud computing,Software development,Software testing etc. Software testing had a Test Manager Manager named Jack he was a very good manager who emphasized on Model Based Testing in which State Transition were checked but the testing team under him was ignorant never listened to what he had to say they did not follow any Tutorial just did what they had to day one faithful day they caused a major mistake due to which most of the testing staff was about to get fired but the Jack Test Manager took the blame that it was his fault and saved his team then the testing team felt guilty about this they started to work as per his directions and improved themselves never making a critical mistake like they had done before.
  • zoim

    The words were:

    Agile Coach / Integration Testing / Alpha Beta Testing / SCRUM

    The story:

    An Agile Coach is responsible for training people to do Integration Testing and Alpha Beta Testing within an agile environment. The whole team is supervised by a SCRUM master, who is responsible for keeping track of the procedures.
  • Stefan Papusoi

    The words were:

    Tester / Domain Testing / Ad Hoc Testing / Agile Principles

    The story:

    One of the main techniques a Tester applied in the testing of a project regarding the data migration was Domain Testing. One programmer in the team had little idea about what that means. To him it seemed a lot like Ad Hoc Testing. The same programmer also had issues with understanding the application of Agile. So later that day a more detailed discussion on Agile Principles and also some various Test Techniques happened between the two of them.
  • James Bach

    The words were:

    Scrum Master / Decision Table Testing / Alpha Beta Testing / Conference

    The story:

    Once there was a Scrum Master who lived all alone in a forest. It was a sad life for this lonely Scrum Master, since he had no one to "Scrum" with. So, one day he decided to go to a testing conference. Now, our Scrum Master, whose name was Werner, had heard of decision table testing before-- that's where you make a table containing input conditions that is mapped to output conditions-- but at the conference he heard about something called "alpha beta Testing." This was strange to him, because he had never heard of that before. He had heard of alpha testing, which is the initial testing performed inside of a team before anyone else sees the product. He had heard of beta testing, which is the kind of testing done informally by users who get a preview of the product. But nowhere in his great forest did any of the animals speak of "alpha beta testing." Eventually, he concluded that the guy who said "alpha beta testing" was probably a little confused, and maybe English was not his first language. So, Werner returned to his cottage in the forest, and where later he saved some girl from a wolf or something. The End.
  • VS_Geenio

    The words were:

    Agile Coach / Domain Testing / Rapid Testing / Conference

    The story:

    During our QA conference, Agile Coach said that rapid testing and domain testing will be involved in our processes next sprint. We found that pretty dismoraling : new activities, but no additional salary.
  • John

    The words were:

    Business Analyst / Error Handling / Test Driven Development / Daily Scrum

    The story:

    On our Daily Scrum meeting about Test Driven Development we are discussed about Error Handling into our project with our Business Analyst.
  • Enikey

    The words were:

    Administrator / Security / Acceptance Testing / Conference

    The story:

    Security Administrator Conference Acceptance Testing
  • Ashrafvali

    The words were:

    Tester / Error Handling / Agile Testing / Agile Manifesto

    The story:

  • Gre4a

    The words were:

    Tester / Compatibility / Test Driven Development / Estimation Meeting

    The story:

    Once apon a time one Tester have a very nice job. He worked for hours and almost find the Compatibility between bugs and programmers code. And he think that he can improve in his company the Test Driven Development. After first project he discuss his improvements on Estimation Meeting.
  • Bogdan Constantinescu

    The words were:

    Test Analyst / System Testing / Testability / Tutorial

    The story:

    There was once an individual who felt passionate about finding flaws in systems - not because he wanted to prove the engineer wrong, but just because he intended to help the engineers make their software not just good, but great. So he started testing these systems through analysis of their behavior rather than just random actions, so his name changed from Tester to Test Analyst. Once all elements of the software had been integrated, he would start System Testing procedures, which were his favorite activity due to the complexity of the paths one had to contemplate. But due to the team not being used to working with QA, the testability of the system was quite low - the application was hard to access, test data was complicated and laborious to create and documentation was scarce. So he had a great idea - to start writing a "How To" for current and future QAs on the project to not tread through the same pitfalls. So, he started writing a QA tutorial which approached all areas of the application and how to test it given its odd nature and quirks.
  • Leonardo

    The words were:

    Tester / Install Uninstall Testing / Code DrivenTesting / eXtreme Programming

    The story:

    A real Tester is the one good with the Install Uninstall Testing. Sometimes it may be useful to use the Code DrivenTesting, otherwise go for the eXtreme Programming.
  • Georgii Zhabieiev

    The words were:

    Test Analyst / Security / Ad Hoc Testing / Planning Meeting

    The story:

    Even our Test Analyst knew that we need to discus security and Ad Hoc testing during last planning meeting.
  • Manby

    The words were:

    Customer / Integration Testing / Exploratory Testing / Agile Manifesto

    The story:

    It is important that a customer is happy with their experience with a product, therefore, integration testing is essential when implementing new features. A checklist of all possible affected areas should be compiled, with each area being tested in full, to ensure functionality has not changed. According to the Agile Manifesto, work should have a quick turnaround with many releases, in this scenario, such a high level of integration testing is impossible to achieve without automated testing. If automation is unavailable, a QA team can rely on exploratory testing, which is more reliant on a testers intuition and experience, leading them towards problematic areas.
  • littlesparta

    The words were:

    Developer / Domain Testing / Test Driven Development / Tutorial

    The story:

    A website developer may use test driven development methods as well as domain testing when working with websites. One method to kick start your career as a website developer is via tutorials.
  • Adinca

    The words were:

    Developer / Decision Table Testing / Rapid Testing / Daily Scrum

    The story:

    After our Daily Scrum meeting we decided to have a chat about the Rapid Testing approach developed by James Bach. The Developer that is currently working with me on the new integration system wanted to take part in our meeting as well. He was very intrigued by the Decision Table Testing that can help reduce the number of needed tests for a complex variation of inputs.
  • Ozz Hart

    The words were:

    Developer / Boundary value analyses / Acceptance Testing / Waterfall model

    The story:

    Working in a games company, testing can often be forgotten about or an afterthought if it is not handled properly. As a tester I also consider myself a developer as well, as the games we make would not be the same without us here! We don't use a Waterfall model here, as we use Agile instead. Every morning the teams stand up and discuss the plan of action for the coming day, and it seems to work quite well. In the testing department we run things separately from the games teams in a way, while still being embedded. Part of the reason for this is because I like to be able to keep the team as a central hub of knowledge, but also because it makes training a lot easier. As part of our training I have been getting the team to do the challenges on this website, and that included both Boundary value analyses for Challenge 6 and Acceptance Testing for Challenge 1. We have found this site extremely useful so far as it promotes technical testing skills, and even though not all of my team can code, I found that the skills they use on a daily basis allowed them to complete a large number of the challenges.
  • Andrey Shkabara

    The words were:

    Developer / Integration Testing / Combinatorial Testing / Training

    The story:

    my Developer said me to check the Integration testing of facebook, then we had done the Combinatorial Testing, and all together went to training.
  • James Osborn

    The words were:

    Test Analyst / Happy Path Testing / Ad Hoc Testing / Budget Meeting

    The story:

    As a Test Analyst, our first instinct is to begin with Ad Hoc Testing - No plan, just sanity check the system for basic issues. From there, we go to formalised Happy Path Testing, to Negative testing and onwards until we reach automation. Some people claim software testing is a waste and this can be done by developers at a lower cost. I would argue such generalising nonsense is best left for executives in the Budget Meeting.
  • cristian

    The words were:

    Business Analyst / Boundary value analyses / Acceptance Testing / Waterfall model

    The story:

    Being a Business Analyst is hard work and during this work one has to make a lot of Boundary value analyses. On the contrary, a tester has to create a lot of tests, one of them being Acceptance Testing. Also, both of them should not work on a project based on the Waterfall model
  • Rai

    The words were:

    Product Owner / Error Handling / Alpha Beta Testing / Budget Meeting

    The story:

    A Product Owner decides that he would like to have a feature. He describes the feature and organizes a Meeting. He asks to come more members to join like Project manager, developer, test analyst to discuss how much effort it can take. Then Product Owner organizes the second meeting which is called Budget Meeting to see how could cost to implement the feature. When it is decided how many developers, testers will work the work starts. Developers start coding and testers start creating test cases and scenarios. Program is ready. Testers start to test it, register defects and developers fixing them. Error Handling is done. After analyzis it was decided that system is ready for the fist release. No one want to give system outside the company yet so it was decided to do Alpha Beta Testing where Alpha Testing will be possible on developers side and on the next release Beta Testing will happen on customers side and be given to the first users. End of the story.
  • 12312312

    The words were:

    Tester / User Experience / Rapid Testing / Daily Scrum

    The story:

    The tester is having an user experience and will create a rapid testing over the project, that will be presented on the daily scrum.
  • Anastasiya Romanenko

    The words were:

    Customer / Install Uninstall Testing / Acceptance Testing / Planning Meeting

    The story:

    Today on the planning meeting customer together with testers carried out acceptance testing and install uninstall testing
  • meee

    The words were:

    Project Manager / System Testing / Code DrivenTesting / SCRUM

    The story:

    Current I'm an intern at a very lovely firm. As an intern I'll be working in a SCRUM team. The Project Manager of the project I'll work all summer is a very interesting person. I've met him yesterday. My position as an intern is to be part of the System Testing team. But also, the Code DrivenTesting is a very important part.
  • MargaritaMedunetskaya

    The words were:

    Product Owner / Decision Table Testing / Crowd Testing / Planning Meeting

    The story:

    At the planning meeting the product owner gave instructions to conduct crowd testing and decision table testing.
  • Womix

    The words were:

    Project Manager / Compatibility / Acceptance Testing / Daily Scrum

    The story:

    In our Daily Scrum, my Project Manager tell me what we need to do Compatibility test before Acceptance testing.
  • kendzi

    The words were:

    Test Manager / Boundary value analyses / Model Based Testing / Daily Scrum

    The story:

    At our team daily scrum our test manager said that he is not happy with model based testing that we use. He said that team forget to include boundary value analyses to the setting.
  • Norbert Zając

    The words were:

    Administrator / Localization / Crowd Testing / Budget Meeting

    The story:

    Administrator hosted a crowd testing which was a budget meeting, but didn't check it's localization anyhow.
  • Rafał

    The words were:

    Product Owner / Compatibility / Testability / Retrospective Meeting

    The story:

    The Product Owner make Retrospective Meeting increase Compatibility and Testability of code.
  • pallavi

    The words were:

    Developer / Security / Test Driven Development / Retrospective Meeting

    The story:

    retrospective meeting security developer test driven development and tester knew how to develop a program and developer has a security to create and code and de code the program and he has to discuss with the retrospective meeting.
  • Timofei Bogolyubov

    The words were:

    Tester / Decision Table Testing / Pair Testing / Daily Scrum

    The story:

    During the latest Daily Scrum we had a discussion on how to improve our testing performance, Testers were suggesting Decision Table Testing technique to simplify test case storage and share them with whole team, whenever developers suggested Pair Testing with them to improve their knowledge of new parts of the system because the project became too large for them to know everything.
  • Anirudh

    The words were:

    Tester / Error Handling / Rapid Testing / eXtreme Programming

    The story:

    A tester is a person who is required to have a good knowledge of manual and automation testing so he can work under the supervision of a test lead and test manager and generate multiple test cases and write scripts for different web based and window based applications. A tester is handed over a module that has been developed and he/she tries to find bugs and defects in the functionality of the module, files a report of the bugs and hands it over to the development lead who further assigns the development engineer to that module, who had already worked on it before. He does error handling and fixes the bugs. Testers are required to do rapid testing and thus automation testing comes into picture. Automation testing allows parallel execution and reduces human intervention and error, which enables testing of multiple test cases at the same time. Coders are expected to do extreme programming and testers are required to do rapid and quick testing to deliver the product in stipulated time.
  • Peter Tarasenko

    The words were:

    Developer / System Testing / Pair Testing / Agile Manifesto

    The story:

    The Agile Manifesto requires Developer to use Pair Testing and QAs to use System Testing
  • Kseniya Krashenitsa

    The words were:

    Agile Coach / Error Handling / Behaviour Driven Development / SCRUM

    The story:

    Behaviour Driven Development isn't an Agile framework or project management approach. Teams using Scrum or Kanban with BDD will need to figure out what to put in their backlogs and boards for planning purposes. In my work as an agile coach, I find many teams applying Scrum are puzzled about user stories. Should the error handling be part of the original user story?
  • dsh

    The words were:

    User / Happy Path Testing / Test Driven Development / Tutorial

    The story:

    We want to have a tutorial Happy path testing should be defined by user before test driven development
  • Mihai Hurduc

    The words were:

    Agile Coach / Happy Path Testing / Data Driven Testing / eXtreme Programming

    The story:

    As an Agile Coach I want to be able to show to QA Engineers and Developers which are the best practices for Happy Path Testing, Data Driven Testing and eXtreme Programming. Acceptance Criteria As a QA engineer I should be able to do Happy Path Testing As a QA engineer I should be able to do Data Driven Testing As a Developer I should be able to do eXtreme Programming
  • Tina

    The words were:

    Developer / Fuzz Testing / Context Driven Testing / SCRUM

    The story:

    Roles on the project are different. Scenarios are different. Also types of approaches too. Developers should develop and fix bugs. Tester should use fuzz testing and Context Driven Testing. And all these processes can be done by SCRUM methodology.
  • dd

    The words were:

    Developer / Domain Testing / Agile Testing / Review Meeting

    The story:

    Hi as a Developer i want perform tests on domain testing and agile testing. should we review the meeting
  • Milton Pereira

    The words were:

    Business Analyst / User Experience / Pair Testing / Tutorial

    The story:

    as a Business Analyst would like to Pair Testing to create a User Experience Tutorial
  • Maria Rusanova

    The words were:

    Tester / Boundary value analyses / Exploratory Testing / Retrospective Meeting

    The story:

    As a Tester I would like to know how to use Boundary value analyses So that I perform Exploratory Testing quickly but with no loss to quality And find defects That will be discussed during Retrospective Meetings
  • Anatoly Ignatov

    The words were:

    Scrum Master / Integration Testing / Testability / Estimation Meeting

    The story:

    Our scrum master scheduled estimation meeting today with integration testing and testability of the app in the agenda.
  • BDjakovic

    The words were:

    Administrator / Boundary value analyses / Rapid Testing / Waterfall model

    The story:

    Boss came to my team with a project that needs to be tested. First of all, Administrator, needed to assemble our PC's so we can work on them. After the PC's were assembled we started testing. First, we used Boundary value analyses, to check the boundary values of numbers that we are testing. After that we used Rapid Testing, to determine more bugs on our complex project, with simple tools. Important thing to say is that we were driven by the Waterfall model, which was the best model to use in our case.
  • Irina Stoica

    The words were:

    Test Analyst / Component Testing / Ad Hoc Testing / Estimation Meeting

    The story:

    We had an Estimation Meeting during which the Test Analyst talked about the Component Testing time needed and the Ad Hoc testing that is not the best way to check new functionalities.
  • GieHa

    The words were:

    Developer / Unit Testing / Rapid Testing / Community

    The story:

    Little Developer does not like make Unit Testing. He likes Rapid Testing by Community.
  • AdB

    The words were:

    Customer / State Transition / Rapid Testing / SCRUM

    The story:

    Project: Timer Dev Approach: SCRUM (iterative and incremental). Test Approach: Rapid Testing Stories: 1. As a Customer I would like to get Timer to be able to measure time with ms precision. 2. As the Timer I would need to have State Transition in order to distinguish start, run, pause and stop modes. 3. As a Customer I would like to read the Timer's Counter in format: hh:mm:ss:msmsms 4. As a Customer I would like to have an opportunity to rapidly test any increment from the scrum development so could have sanity checks after every sprint. 5. As a Customer I would like to have a chance to add some changes in every SCRUM sprint so I could adjust the final solution to the desired quality and expectations.
  • Ilona

    The words were:

    Tester / Install Uninstall Testing / Alpha Beta Testing / Budget Meeting

    The story:

    Tester was doing Install Uninstall Testing on Alpha Beta Testing during Budget Meeting.
  • Bzyku

    The words were:

    Tester / Domain Testing / Combinatorial Testing / Conference

    The story:

    Conference in Dortmund. Some Tester talk about Domain Testing. Developer talk about Combinatorial Testing.
  • Ernesto Ivanovich

    The words were:

    User / Localization / Testability / Conference

    The story:

    When the boring CONFERENCE call is over, I have to work on the japanese LOCALIZATION of the TESTABILITY analysis which needs to be USER-friendly
  • Ttt

    The words were:

    Developer / Integration Testing / Testability / Waterfall model

    The story:

  • alex

    The words were:

    Test Analyst / Cause And Effect Testing / Exploratory Testing / Conference

    The story:

    Last monday we had a QA conference where we were learning about cause and effect testing, exploratory testing and some test analyst in this areas.
  • Volodymyr Kyrychenko

    The words were:

    Tester / System Testing / Code DrivenTesting / Training

    The story:

    As a senior QA on the project i was tasked to conduct training among junior and middle testers regarding System Testing and Code DrivenTesting techniques.
  • Alexandra Pavlova

    The words were:

    Project Manager / Component Testing / Combinatorial Testing / Agile Principles

    The story:

    A Project Manager has to understand what the difference between Component Testing and Combinatorial Testing is. The is essential part of the Agile Principles.
  • Michal Foksa

    The words were:

    Project Manager / Test Automation / Model Based Testing / Daily Scrum

    The story:

    given project manager require test automation then test automation is based on model based testing and we report it on daily scrum meetings
  • Milena Ryapova

    The words were:

    Scrum Master / Localization / Behaviour Driven Development / Conference

    The story:

    Story for daily task plan for morning meeting : * connect to Scrum Master to discuss new method for client Localization using new maps for our application. * Also give estimation for new integration of Behaviour Driven Development in automation tests * Prepare strictly technical presentation of our new application and used tools that will present at QA Conference next month
  • LL #qachallenge

    The words were:

    Product Owner / Localization / Ad Hoc Testing / Retrospective Meeting

    The story:

    Product Owner was not happy during the Retrospective Meeting that QAs tested the Localization only with Ad Hoc Testing and did not apply any black box testing technique.
  • Georgi Ivanov #qachalleng

    The words were:

    Test Manager / Integration Testing / Ad Hoc Testing / Training

    The story:

    The Test Manager was part of the interview process for the new candidate in the QA team. The manager explained in details what the new employee responsibilities will be and assured him that there will Training in the first month or so. In addition the test manager gave the new employee a hint to read as much as he can on Integration Testing and Ad Hoc Testing, as those will be part of his new duties.
  • LLAlive

    The words were:

    User / Integration Testing / Code DrivenTesting / Agile Principles

    The story:

    If you are more than a User than you should know Agile Principles. They allows you to do all types of testing (like Code DrivenTesting or Integration Testing) with maximum effecient.
  • Alex

    The words were:

    Administrator / Fuzz Testing / Data Driven Testing / Training

    The story:

    Administrator have done the Fuzz Testing. At this time a couple of testers, who have been finished their Training, have started the Data Driven Testing. After all they went to the bar and purchased great espresso coffee.
  • Lily

    The words were:

    Business Analyst / User Experience / Test Driven Development / Estimation Meeting

    The story:

    There was a really good speech from our Business Analyst about User Experience and Test Driven Development on the Estimation Meeting.
  • Johan

    The words were:

    Administrator / Performance / Rapid Testing / Agile Manifesto

    The story:

    As an administrator, i would first recheck the instruction challenge. It contains multiple typo's which are on a site about testing unacceptable. Secondly, I would check if the performance of the clock cannot be manipulated. Heck.. one might give himself 200 minutes. Rapid testing was invented by James Bach.. but then again.. who can invent was was already common sense. The agile manifesto is whatever the company wants it to be it seems. I've seen all sorts of things come by over the years and none of it is correct. Perhaps that's the way it was meant to be.
  • Mark Soriano Porcalla

    The words were:

    Tester / Fuzz Testing / Test Driven Development / Daily Scrum

    The story:

    Testers discussed some Test Driven Development for the new testers for their Fuzz Testing and Daily Scrum.
  • kiko

    The words were:

    Scrum Master / System Testing / Agile Testing / Agile Manifesto

    The story:

    The Scrum Master is the one responsible for stand up meetings. The Agile Manifesto is an important guideline when doing the Agile Testing. Once unit tests are finished, System Testing is the final phase of testing to ensure efficient test.
  • Felis

    The words were:

    Administrator / Localization / Crowd Testing / Budget Meeting

    The story:

    Tomorrow all the administrators will held a budget meeting. None of them know that due to the company localization the managers came up with the idea of crowd testing. Thus all of the participants will be observed and their behavior will be later analyzed. Will some of the administrators be fired? Who knows.
  • Tatyana

    The words were:

    Test Manager / Component Testing / Context Driven Testing / Planning Meeting

    The story:

    Today we had Planning Meeting, during the meeting the Team Test Manager introduced the Idea to use Component Testing for some projects and Context Driven Testing.
  • shadowscatcher

    The words were:

    User / Fuzz Testing / Agile Testing / Waterfall model

    The story:

    I found myself on some strange website, that wants me to imagine a story with words like "user", "fuzz testing", "agile testing" and even "waterfall model". The funny thing here - I obey.
  • Quah Shiwei Dave

    The words were:

    Product Owner / Component Testing / Ad Hoc Testing / Community

    The story:

    The product owner requires the development and testing team to carry out component testing as well as ad hoc testing before release to the community.
  • Bharath.S

    The words were:

    Customer / Decision Table Testing / Pair Testing / Community

    The story:

    as a customer I shoulid be able to use the decision table testing and pair testing with my community
  • Julia Osinkina

    The words were:

    Product Owner / Integration Testing / Exploratory Testing / Waterfall model

    The story:

    Today Product owner told us that starting next month we will switch from waterfall model to agile. He also mentioned importance of integration testing and emphasized that test team should spend more time on exploratory testing.
  • SzP

    The words were:

    Administrator / Performance / Rapid Testing / Retrospective Meeting

    The story:

    Conclusions from retrospectie meeting: Administrator need to do rapid testing to check performance.
  • vodka

    The words were:

    User / Compatibility / Combinatorial Testing / Community

    The story:

    It is widely known among the testing community that it is important to perform combinatorial testing to get rid of compatibility issues in order to achieve maximum user's satisfaction.
  • IrisOnika

    The words were:

    Customer / Integration Testing / Testability / Estimation Meeting

    The story:

    On estimation meetimg test lead discussed with our customer cooperation plan for integration testing and also talked about the testability of the whole project
  • APHD

    The words were:

    Project Manager / Operational Readiness / Rapid Testing / Tutorial

    The story:

    A new version of the product is set to go live in weeks. The Project Manager is concerned that not everything will be done in time and tested properly. The QA team is engaging in Rapid Testing to find the most important bugs quickly so they are focusing as much as possible on risk. But the company as a whole is worried about operational readiness, whether or not the product will work as it should, be compatible with all of the important platforms, be able to handle the expected user load, and even be documented with a tutorial and FAQs should users need help. But everyone is working together and communicating well to deliver everything on time and give their customers something they'll love.
  • QA cum Coder

    The words were:

    Test Manager / Install Uninstall Testing / Test Driven Development / Conference

    The story:

    In a Conference, the Test Manager explained about Test Driven Development and showed how to Install Uninstall Testing Techniques.
  • ToddR

    The words were:

    Developer / Install Uninstall Testing / Testability / Community

    The story:

    The QA Community as a whole relies upon the Developer to provide code that has good Testability. Code that can't be easily tested is bound to have errors. Including Install Uninstall Testing is essential to quality.
  • Razvan Inca

    The words were:

    Agile Coach / Performance / Agile Testing / Budget Meeting

    The story:

    The tester asked the agile coach about agile testing performance during the budget meeting
  • Vaim Raisk

    The words were:

    Test Manager / Integration Testing / Behaviour Driven Development / Planning Meeting

    The story:

    Yesterdays planning meeting did not go very well. Test manager was only talking about integration testing while project managers were so excited about Behaviour driven development that they forgot to mention what project they were talking about.
  • KOYNOYNO

    The words were:

    Test Analyst / Performance / Alpha Beta Testing / SCRUM

    The story:

    Test Analyst checked Performance of Alpha Beta Testing due to SCRUM scenario.
  • Alakaganaguathoork

    The words were:

    Test Analyst / Operational Readiness / Behaviour Driven Development / Budget Meeting

    The story:

    While I'm as the Test Analyst writing this text, Operational Readiness is trying to get a clue, what a Behavior Driven Development is and why a Budget Meeting is so important for our CEO
  • Anton Striga

    The words were:

    Customer / Boundary value analyses / Exploratory Testing / Daily Scrum

    The story:

    During the daily scrum the customer asked the question why the QA engineers doesn't implement the boundary value analyses in the exploratory testing.
  • Iris Onika

    The words were:

    User / Happy Path Testing / Acceptance Testing / Review Meeting

    The story:

    At the Review Meeting it was decided to spend only Happy Path Testing due to lack of time.  Acceptance Testing we had to entrusted to our customer's user.
  • Alexey Prystavko

    The words were:

    Tester / Cause And Effect Testing / Test Driven Development / Daily Scrum

    The story:

    In the daily Scrum meeting, testers will tell us about Test Driven Development and Cause And Effect Testing
  • Oleksandra

    The words were:

    Customer / Localization / Data Driven Testing / Agile Manifesto

    The story:

    A Data Driven Testing was held according to Agile Manifesto. The Customer was informed about the defect localization.
  • Titirca Silviu

    The words were:

    Developer / Fuzz Testing / Rapid Testing / Community

    The story:

    As a Developer I would like my implementation be tested using Rapid Testing all the time and when required also Fuzz Testing so that I can share the testing results to the Community.
  • Alex Kokhanchuk

    The words were:

    User / Integration Testing / Combinatorial Testing / Planning Meeting

    The story:

    On planning meeting I got issue to test story using user positive testing. Than execute Integration Testing and Combinatorial Testing for current story.
  • Andrada Banica

    The words were:

    Administrator / Localization / Exploratory Testing / Training

    The story:

    As a tester, I do often exploratory testing. Sometimes I need to login in to an application using the administrator role and test the localization. For that, I had some training from a senior tester.
  • Kasia

    The words were:

    Test Analyst / Domain Testing / Context Driven Testing / Estimation Meeting

    The story:

    As I am Test Analyst, I often prepare test cases for my clients. I usually use Domain Testing. Of course, all is based on context and Clients demands. More popular in my company is Context Driven Testing, as a new methodology we implement to our daily work. When we meet with client, we prepare offer, table with prices and we present it on estimation meeting. Usually, we have to improve it and make some changes according to client demands, but it takes a few days.
  • Monster

    The words were:

    Customer / Compatibility / Combinatorial Testing / Tutorial

    The story:

    Make tutorial with combinatorial testing to check system compatibility for customer.
  • Yaroslav Novak

    The words were:

    Test Manager / Error Handling / Acceptance Testing / Conference

    The story:

    Our Test Manager when he participated in Scrum Conference talked about the necessity of Error Handling and Acceptance Testing
  • Gordon Crawford

    The words were:

    Tester / Happy Path Testing / Pair Testing / eXtreme Programming

    The story:

    As a tester your role is not just to perform Happy Path Testing, this will probably be covered by the developers if they are following the eXtreme Programming methodology, but to poke and pro the edges to find where there may be problems. This can be difficult for new testers to understand but a good way to help them learn is through Pair Testing where you can show them how you would test and the thought processes you go through when testing an issue.
  • Tomasz Szyborski

    The words were:

    Developer / State Transition / Testability / Review Meeting

    The story:

    The Developer with the Tester thought about improving Testability of given piece of software. First, they attended brainstorming meeting, on which few ideas have appeared. On of which was automating the test using gherkin syntax, then the Tester thought about boundary value testing with equivalence partitioning. The Developer nodded, but they both felt that something was lacking. In the end - two more ideas popped into their mind - they should include Decision Table and State Transition testing to create cases to be put into test management tool. They called Project Manager and other teammates to arrange Review Meeting.
  • Jason

    The words were:

    Project Manager / Performance / Context Driven Testing / Estimation Meeting

    The story:

    The Project Manager is looking for us to come up with our estimations for doing some performance testing. Unfortunately we have one day before the estimation meeting. Having little other information on the SUT we will need to use a context driven testing approach.
  • t.yasiuk

    The words were:

    Tester / Localization / Alpha Beta Testing / Agile Manifesto

    The story:

    Once upon a time there lived a tester. He had to test Localization during Alpha Beta Testing. He wanted to act traditionally, basing on thorough documentation. But he was only shown the Agile Manifesto. So he had to deal with a new type of work in new conditions. He read the Manifesto, asked his colleagues and finally liked agile working. So he did Localization testing properly and became a par of an agile team.