For 30 years, the EuroSTAR Software Testing Conference has been the largest gathering of software testing and QA professionals in Europe. The testing community come together at #EuroSTARConf to learn from world class speakers, make powerful connections and be inspired with new ideas. EuroSTAR also host a comprehensive software testing content site, EuroSTARHuddle.com for free online learning resources, co-created by the community.
The EuroSTAR Community is diverse and at our in-person events you will meet testers from over 50 countries, across all industries and from varying fields of thought. Our events are open to all software professionals - particularly those with a passion for software testing, quality assurance and Test Automation - regardless of your approach to testing, your chosen school of thought, your affiliations or accreditation.
#EuroSTARConf, 11-14 Jun 2024, Stockholm, Sweden. #AutomationSTAR, 20-21 Nov 2023, Berlin, Germany.
because it's a few days until 11th June, i recommend to read Andreas Zeller's book 'Why Programs Fail' in the meantime. Testing effort should go into the hotspots, the dark corners, where the bugs live.
Powiem krotko - jestem bardzo dumny z Ciebie i z tego co osiągnęłaś. Wyrosłaś na piękną kobietę i bardzo miło zobaczyć Cię w dorosłym życiu:) Gratuluję sukcesu o bardzo się cieszę.
All sensational points! I would also say "Communication" - and purely for the Tester (vs. Test Manager) I would add bonus skill, that was not important enough to be mentioned along the great points in the video: enjoy repetitive work every now and then. This is not meant negatively! Sometimes you have to repeat the same tasks and test cases days and weeks in a row, and that's okay, too. The last guy with the agile stuff is the best one though => use your head and heart and not some BS hype
Wow... some serious scare mongering going on here - "Can you afford not to?" This is gross. Is Stuart invested financially in people taking up this standard?
I agree that communication is the most important attribute of a Tester. Furthermore, have as much knowledge as possible of what you're going to test and ask questions, even if the question may sound "dumb" because you are the one responsible for saying yay or nay that either a certain software piece or the entire software is ready for production.
There are so many important skills to be a Tester. In my opinion these 3 below skills are key. + critical thinking. + Problem solving. + Communication When you get bugs, you should try find out the problem behind the issue. What is logical, technical issues causing bugs, if you're able to find it down, you can describe the bug which is clearer and this is both Communication and Problem solving skills, when you're in rush situation, you need to know how to create solution and raise the current situation and testing solution that is suitable. Yeah there are more and more skills to say.
First of all, you need to have a keen observation sense, second of all you need to have a talent for testing various possibilities, communication is useless without the first two.
Depends, in my experience which is mostly bug detecting and reporting i would say communication which needs to be clear and effective but also the classic one which is eye for detail for improvements and finding the errors flaws bugs etc
In summary, The three things as most important for testing are: 1. *Attributes:* the adverbs and adjectives that describe the high-level concepts testing is meant to ensure. Attributes such as fast, usable, secure, accessible, and so forth. 2. *Components:* the nouns that define the major code chunks that comprise the product. These are classes, module names, and features of the application. 3. *Capabilities:* the verbs that describe user actions and activities. Also referred to as ACC. This article is a good companion to this video: testing.googleblog.com/2011/09/10-minute-test-plan.html
That's the developer aproach normaly. The QA is more involved with the product owner as an extent of his capacity, so the QA most likely is just trying to build a better product.
As part of the video, you mentioned that API testing can also be used to identified that how much developer's code has been covered by my API Testing. Are there any tools available for this functionality which can test the code coverage my test case has done?
the most important skills for tester is to understand the requirement business logic,functional flow,impacts for completing work and communication is also important but communication doesn't have any priority in skills......tester work talk not a communication......................if someone good in communication but poor in knowledge then he/she cant be a professional tester.
