Testing Challenge #7 was completed by
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
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.
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.
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.
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.
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.
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.
The words were:Administrator / Security / Acceptance Testing / Conference
The story: Security Administrator Conference Acceptance Testing
The words were:Tester / Error Handling / Agile Testing / Agile Manifesto
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.
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.
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.
The words were:Test Manager / Portability / Testability / Planning Meeting
The story: Our Test manager Maria pay attention to importance of portability and testability of new features
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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
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.
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.
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.
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.
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.
The words were:Product Owner / Compatibility / Testability / Retrospective Meeting
The story: The Product Owner make Retrospective Meeting increase Compatibility and Testability of code.
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.
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.
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.
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
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?
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
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.
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
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.
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
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
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
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.
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.
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.
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.
The words were:Customer / State Transition / Rapid Testing / SCRUM
The story: Project: Timer
Dev Approach: SCRUM (iterative and incremental).
Test Approach: Rapid Testing
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.
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.
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.
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
The words were:Developer / Integration Testing / Testability / Waterfall model
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.
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.
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.
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 #qachallen
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
The words were:Administrator / Performance / Rapid Testing / Retrospective Meeting
The story: Conclusions from retrospectie meeting: Administrator need to do rapid testing to check performance.
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.
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
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.
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.
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
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.
The words were:Test Analyst / Performance / Alpha Beta Testing / SCRUM
The story: Test Analyst checked Performance of Alpha Beta Testing due to SCRUM scenario.
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
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.
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.
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
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.
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.
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.
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.
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.
The words were:Customer / Compatibility / Combinatorial Testing / Tutorial
The story: Make tutorial with combinatorial testing to check system compatibility for customer.
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
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.
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.
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.
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.