Filter
Exclude
Time range
-
Near
In this agentic world, my prospection is closer to become true #ai #exploratoryTesting
The easiest solution to make a build green is "rm -fr ./tests". Also best for long-term maintenance #Testing #QA
1
84
Exploratory testing is not ad-hocโ€”itโ€™s disciplined and strategic. Agree or disagree? Share your take ๐Ÿ‘‡ #ExploratoryTesting #QALife #SoftwareTester
2
29
1 Aug 2025
AI is everywhere, but can it truly enhance our testing performance and efficiency? Join @gil_zilberfeld, CTO, TestinGil, in an engaging session at #TestMuConf 2025 ๐Ÿ”— bit.ly/TestMUConference2025 Watch Gil talk about how AI can help with its different aspects of #ExploratoryTesting and learn how to use our time effectively, using current #AITools. Join us at #TestMuConf 2025 from August 19-21, and level up your #testing strategies! #Conference #SoftwareTesting #TestAutomation
1
3
103
How do you test an application with no documentation? #ExploratoryTesting #ManualTesting #SoftwareTesting #AutomationTesting
1
2
48
๐Ÿงช ๐Œ๐€๐๐”๐€๐‹ ๐“๐„๐’๐“๐ˆ๐๐† ๐’๐„๐‚๐‘๐„๐“๐’ ๐๐Ž ๐Ž๐๐„ ๐“๐„๐‹๐‹๐’ ๐˜๐Ž๐” ๐Ÿ” Because not all bugs live where you expect themโ€”and not all tests should be scripted. Manual testing isnโ€™t just clicking around a UIโ€”itโ€™s a strategic, creative, and often instinctive process. Hereโ€™s a scroll-worthy breakdown of the lesser-known secrets that ๐ฌ๐ฆ๐š๐ซ๐ญ ๐ญ๐ž๐ฌ๐ญ๐ž๐ซ๐ฌ ๐ฎ๐ฌ๐ž ๐ญ๐จ ๐ฎ๐ง๐œ๐จ๐ฏ๐ž๐ซ ๐œ๐ซ๐ข๐ญ๐ข๐œ๐š๐ฅ ๐ข๐ฌ๐ฌ๐ฎ๐ž๐ฌ: ๐Ÿงญ ๐„๐ฑ๐ฉ๐ฅ๐จ๐ซ๐š๐ญ๐จ๐ซ๐ฒ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  Test without a script. Discover without a roadmap. Leverages human intuition to uncover bugs automation misses. ๐Ÿชฒ ๐“๐ก๐ž ๐๐ž๐ฌ๐ญ๐ข๐œ๐ข๐๐ž ๐๐š๐ซ๐š๐๐จ๐ฑ Running the same test repeatedly wonโ€™t catch new bugs. Mix it up, or defects start hiding in plain sight. ๐Ÿ”€ ๐‹๐š๐ญ๐ž๐ซ๐š๐ฅ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  Test workflows sidewaysโ€”out-of-sequence, edge flows, non-standard inputs. Thatโ€™s where bugs like to live. ๐Ÿ“Š ๐“๐ก๐ž ๐Ÿ–๐ŸŽ/๐Ÿ๐ŸŽ ๐‘๐ฎ๐ฅ๐ž ๐จ๐Ÿ ๐๐ฎ๐  ๐ƒ๐ข๐ฌ๐ญ๐ซ๐ข๐›๐ฎ๐ญ๐ข๐จ๐ง 80% of bugs are found in 20% of the modules. Know where your code is fragileโ€”and test it harder. ๐Ÿงณ ๐“๐ก๐ž "๐“๐จ๐ฎ๐ซ๐ข๐ฌ๐ญ" ๐€๐ฉ๐ฉ๐ซ๐จ๐š๐œ๐ก Pretend youโ€™re a first-time user. Click like you're curious, not cautious. Youโ€™ll spot usability flaws automation never will. ๐Ÿ“ ๐๐จ๐ฎ๐ง๐๐š๐ซ๐ฒ ๐•๐š๐ฅ๐ฎ๐ž ๐€๐ง๐š๐ฅ๐ฒ๐ฌ๐ข๐ฌ Donโ€™t just test the middle. Push limitsโ€”min, max, just below, just above. Thatโ€™s where systems crack. ๐Ÿง  ๐‡๐ž๐ฎ๐ซ๐ข๐ฌ๐ญ๐ข๐œ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  Use mental shortcuts and past bug patterns to ๐ฉ๐ซ๐ž๐๐ข๐œ๐ญ ๐ฐ๐ก๐ž๐ซ๐ž ๐ข๐ฌ๐ฌ๐ฎ๐ž๐ฌ ๐š๐ซ๐ž ๐ฅ๐ข๐ค๐ž๐ฅ๐ฒ ๐ญ๐จ ๐š๐ฉ๐ฉ๐ž๐š๐ซ. Experience is your framework here. ๐Ÿ’ฅ ๐ƒ๐ž๐Ÿ๐ž๐œ๐ญ ๐‚๐š๐ฌ๐œ๐š๐๐ข๐ง๐  A minor bug today becomes a major crash tomorrow. Manual testers spot these early-stage tremors before they grow. ๐Ÿค– ๐Œ๐š๐ง๐ฎ๐š๐ฅ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  ๐‚๐š๐ง ๐Œ๐ข๐ฆ๐ข๐œ ๐€๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง Scriptless doesnโ€™t mean mindless. Reproducible steps, checklist-based tests, structured dataโ€”๐ฒ๐จ๐ฎ ๐œ๐š๐ง ๐›๐ซ๐ข๐ง๐  ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐๐ข๐ฌ๐œ๐ข๐ฉ๐ฅ๐ข๐ง๐ž ๐ญ๐จ ๐ฆ๐š๐ง๐ฎ๐š๐ฅ ๐ญ๐ž๐ฌ๐ญ๐ข๐ง๐ . ๐Ÿ“† ๐’๐ž๐ฌ๐ฌ๐ข๐จ๐ง-๐๐š๐ฌ๐ž๐ ๐“๐ž๐ฌ๐ญ๐ข๐ง๐  Short, focused bursts of testing under time constraints post-session analysis = creative accountable testing. ๐Ÿ’ก ๐–๐š๐ง๐ญ ๐ฆ๐š๐ง๐ฎ๐š๐ฅ ๐ญ๐ž๐ฌ๐ญ๐ข๐ง๐  ๐ญ๐ก๐š๐ญโ€™๐ฌ ๐ฉ๐ซ๐จ๐š๐œ๐ญ๐ข๐ฏ๐ž, ๐ง๐จ๐ญ ๐ฃ๐ฎ๐ฌ๐ญ ๐ซ๐ž๐š๐œ๐ญ๐ข๐ฏ๐ž? ๐๐‚ ๐ƒ๐จ๐œ๐ญ๐จ๐ซ๐ฌ ๐๐„๐“ ๐›๐ซ๐ข๐ง๐ ๐ฌ ๐ก๐ฎ๐ฆ๐š๐ง ๐ฅ๐จ๐ ๐ข๐œ ๐ญ๐ž๐ฌ๐ญ ๐ฌ๐ญ๐ซ๐š๐ญ๐ž๐ ๐ฒ together to uncover hidden defects, edge-case scenarios, and experience-breaking issuesโ€”before your users do. ๐Ÿ“Œ Letโ€™s elevate your QA, one secret at a time. ๐ŸŒ pcdoctorsnet.com ๐Ÿ“ž 1 (346) 355-6002 #ManualTestingSecrets #ExploratoryTesting #SmartQA #TestBeyondTheScript #UXQualityMatters #BoundaryValueAnalysis #SoftwareTestingTips #DefectDetection #ManualTesting #SoftwareQuality #TestSmarter #WebTestingTools #BugHunters #QAMatters #UsabilityTesting #texas #usa #UnitedStates #pcdoctorsnet #canada #india
1
2
23
9 Jun 2025
Get ready to dive into Exploratory Testing with AI!๐Ÿ” Join @gil_zilberfeld, CTO, TestinGil at #TestMuConf 2025 ๐Ÿ”— bit.ly/TestMUConference2025, where he discusses the core components of exploratory testing and showcases how AI can optimize each aspect - from charter creation to case suggestion, prioritization, and bug reporting. Book your free spot now at #TestMuConf and learn how AI can streamline documentation, improve test efficiency, and manage workloads effectively. #AI #ExploratoryTesting #QualityAssurance #AITesting #SoftwareTesting
2
3
129
19 May 2025
Tired of hunting down physical #Chromebooks for testing? Introducing virtual ChromeOS Support ๐Ÿ”— bit.ly/4dki6H8 for #ExploratoryTesting in real-time. Say goodbye to: โœ“ Limited physical device access โœ“ Inconsistent test results โœ“ Costly Chromebook test labs โœ“ Geographic testing bottlenecks Whether you're revolutionizing #EdTech or powering enterprise solutions, instantly step into your users' digital shoes and review your app with our virtual ChromeOS environments. #LambdaTestYourApps #SoftwareTesting
3
6
180
The next webinar "Exploratory Testing with AI". We'll talk about how AI can help with: Charter and case suggestion, documentation, bug reporting, and lots more. Wednesday, Apr-23, 10am CET Register now! us02web.zoom.us/webinar/regiโ€ฆ #Testing #Automation #exploratorytesting #charters
2
2
47
Exploratory testing is more than just clicking around it's about uncovering hidden issues, improving user experience, and ensuring a seamless platform for users. #SoftwareTesting #ExploratoryTesting #QATesting #UserExperience #BugHunting #Tech #HNGInternship
3
200
Did you know? Exploratory testing combines learning, test design, and test execution in an iterative process. It's a powerful technique for uncovering unexpected issues. #ExploratoryTesting #SoftwareTesting
2
22
10 Jan 2025
Hay ocasiones en las que tenemos que probar un producto de forma inmediata y no tenemos tiempo de averiguar suficiente informaciรณn, sin embargo, si tenemos que encontrar errores importantes antes de que sea demasiado tarde. En el siguiente Miรฉrcoles de QA minders nos acompaรฑa Pedro Flores quiรฉn nos va a contar acerca de su experiencia en el entrenamiento en Rapid Software Testing Explored (RST Explored) y cรณmo el ahora realiza pruebas exploratorias en su proyecto. No te los pierdas, te esperamos el miรฉrcoles a las 7pm Conoce mรกs de esta metodologรญa aquรญ: rapid-software-testing.com/rโ€ฆ #QAminders #QAminds #SoftwareTesting #PruebasManuales #PruebasExploratorias #ExploratoryTesting #SoftwareDevelopment #softwaretesters #astrazeneca
1
2
107
#TestEvolve: Testing Reimagined Blend manual exploration with automated testing. Capture every insight, track every session, transform your quality assurance approach. Visit: testevolve.com/session-basedโ€ฆ #testing #agile #quality #exploratorytesting
1
3
22
๐ŸŽ™๏ธ "Testing APIs is simple!" ๐Ÿ˜… Said no one ever..until now! In our latest QA Therapy Podcast, we dive deep into API testing, exploratory testing, and contract testing with @WuigPrescott . ๐ŸŽง Listen here: youtube.com/watch?v=8gbIU0MRโ€ฆ #APITesting #ExploratoryTesting #ContractTesting

1
48
1 Nov 2024
๐Ÿ“š These 5 must-read exploratory testing books will help you uncover hidden bugs, refine your strategies, and tackle complex systems like a pro! ๐Ÿš€ ๐Ÿ‘‰ Check out the full list: hubs.ly/Q02Vr_5p0 #ExploratoryTesting #SoftwareTesting #QA #TechLeaders #ContinuousQuality

2
861
Boris Arapovic joins the TestGuild podcast to share how #securitytesting should be part of every #QE's toolkit. Learn how to use #SonarQube, conduct #exploratorytesting, and build a holistic #security approach. ๐Ÿ‘‰ testguild.com/podcast/automaโ€ฆ #cybersecurity #TestGuildPodcast

ALT Why Security Testing is an important skill for a QEs with Boris Arapovic for the TestGuild Automation podcast by Joe Colantonio

1
3
209
๐Ÿ’กExploratory Testing โ€“ The art of uncovering bugs by exploring the unknowns, catching the bugs before they catch you.๐Ÿ› #ExploratoryTesting #SoftwareTesting #ManualTesting #AgileTesting #QualityAssurance #SoftwareDevelopment
1
1
48
I've written this article on data and #ExploratoryTesting. We can use data as a driver for brainstorming new test ideas and expanding existing ones. Feel free to add your own view on how you use data to somehow guide your #testing :) hubs.li/Q02HZQTY0 #softwaretesting #QA

1
3
129
3 Jul 2024
Explaining Exploratory Testing with a Real-Life Scenario: A Child Sent to Buy a Product at the Market Exploratory testing is like going shopping for groceries without a specific list. Hereโ€™s how it works in simple terms: Scenario: A Mother Sending Her Child to Buy Milk at the Market Background: A mother sends her child to the local market to buy a carton of milk. This task involves several steps, choices to make, unforeseen issues, and potential unexpected situations, much like exploratory testing in software. Step 1: The Task Before the child leaves, the mother gives a brief overview of the task: โ€œGo to the market and buy a carton of milk.โ€ This is similar to setting a goal for exploratory testing. The child knows the main objective but not every detail of how to achieve it. Step 2: Prepare for the Task - The child ensures he has money with him in order to execute the task. - The child is aware of the goal and some requirements to achieve it but remains open to exploring different paths to achieve it. - The child thinks of which market he should go to and other alternatives Step 3: Explore the Market - Upon arriving at market, the child starts looking for stores that sell milk and also pays attention to signs, prices, and other products. - The child notices the layout of the market, which shops have discounts, and where the dairy section might be. - The child might ask a shopkeeper for directions or check different brands of milk to compare prices and quality. This exploration is akin to exploratory testing, where the tester navigates through the application without a strict script, observing and interacting with various elements. Step 4: Make Decisions on the Fly The child faces several decisions: - Choosing the Shop: The child sees multiple shops selling milk. Which one looks the most reliable? - Choosing the Product: The child sees different types of milk, some are liquid while others are powdered milk. Which one looks the most reliable? - Evaluating Options: Some cartons are cheaper but near their expiration date. Should the child buy a fresh but more expensive one? These decisions are like the tester deciding which areas of the software to explore deeper based on initial findings. If you find a part of the application that seems confusing, you spend more time testing it to understand its behavior. Step 5: Handle Unexpected Situations The child encounters an unexpected situation: the usual brand of milk is out of stock or the only type of milk available is powdered . The child has to decide: - Alternative Solution: Should they buy a different brand, or call the mother for advice? This mirrors handling unexpected issues in exploratory testing, where the tester finds bugs or behavior that wasnโ€™t anticipated and needs to decide how to proceed. If you encounter an error or something that doesnโ€™t work as expected, you try different ways to reproduce it. You might find features that werenโ€™t documented or that behave differently than anticipated. Step 6: Completing the Task Finally, the child buys a carton of milk, perhaps not exactly as initially planned but with all necessary considerations made. They return home with the milk and inform the mother about their experience, including any issues faced. - You finish the session with valuable insights about how the application works, what issues need to be addressed, and potential areas for improvement. - Your findings help improve the overall quality of the software. #Exploratorytesting #SoftwareTesting #QualityAssurance, #TestersJourney, #TestingMindset #QACommunity, #TestingWisdom #QaTechBro
5
73