testing
Question
|
Testing that credit cards work with a retail POS system How have others been able to test a physical credit card on a POS system? Do you use your own card? Do you get a company credit card and expense everything? Is there a company you can purchase something like this from? |
||
 |
Strengthening System Resilience with Chaos Engineering Testing continuous technological change can seem like chaos. There are many challenges that need to be managed, such as unavailability of power, excessive temperature, incorrect configuration, unexpected behavior of services, network downtime, and processing slowdown in production. By deliberately engineering chaos, we’ll be able to discover many of our systems’ weaknesses before our users do. |
|
|
Can software be too complex for end to end test automation? We have a very complex software product that is installed and runs on a Computer or Server. The Software is managed by a Management Console in the Cloud. For years all of our End to End testing was manual. But this was very resource intensive and time comsuming. So a couple of years ago we moved to a more agule development approach and built a test automation system to run these End to End tests. However, we quickly found limitations for example we couldn't have automated tests check what is being displayed in the UI running on the Computer, or check what is being displayed in the Management Console in the Cloud. So we can never fully replicate in automation what the manual tests were doing. |
||
 |
Fitting In Regression Testing by Shifting QA Left Fixing a bug in one area of the software may break something in another area. To detect whether defects have been introduced, we need to perform regression testing—executing certain test cases again to see whether a change has affected other existing features. But how do you make time for another testing cycle prior to every production release? You need to get QA involved earlier in the software development lifecycle. |
|
 |
Testing in Production: A Conversation with Talia Nassi
Podcast
Talia Nassi, developer advocate at Split Software, chats with TechWell community manager Owen Gotimer about the fears, myths, and benefits of testing in production and how to get your stakeholders on board. Continue the conversation with Talia (@Talia Nassi) and Owen (@owen) on the TechWell Hub (hub.techwell.com)! |
|
 |
False Errors in Test Tooling Traditional GUI automation is linear; it follows a set of steps. The first time you run it, it can't add any value, as the feature isn't done until the automation runs. Once test automation runs a second time, it effectively becomes change detection. This leads to a large number of "failures" that are not actually failures. Whether they are false positives or false negatives, we need a way to fix the automation tooling. |
|
|
how to get strong base for manual testing? what are best resources? I am new to testing and my mentor at the company is asking me to get my base strong with regards to manual testing. I know java and made few demo projects with selenium - browser automation and rest assured - API testing . They are expecting me to have better test cases coverage and base needs to be strong . So , anybody knows few blogs/resources from which I can get my foundation strong?
|
||
 |
5 Steps to Getting Started with Risk-Based Testing Risk-based testing is an approach to testing that helps us handle our limited resources. It’s also a valid model for years to come because it focuses testing resources where they can have the most impact—regardless of whether limitations are due to budget, tight schedules, or even the uncertainty of an unexpected situation like COVID-19. Here are some practical tips, examples, and steps you can use to adopt risk-based testing. |
|
|
What are best practices to perform regression testing successfully in a waterfall and agile project? In live agile and waterfall project, how can we perform regression testing successfully ? which test cases we need to execute and how to maintain the regression testing folder ? should we do full regression testing or partial regression? how to prioritise regression testing if time is less? what are the best practices to successfully do regression testing in a agile project |
||
 |
How to Respond to Retest Requests without a Clear Bug Fix After finding and reporting a bug, a tester may get this response from a developer: "Please rerun the test on the latest version of the code and check if the bug still reproduces." This seems like a rational request; just as a change can cause a bug to appear, it can also fix a bug. But is following up the responsibility of the tester or the developer? And if the bug is no longer there, how do you classify and close it? |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.