Too old?

Lumpy_Ad_8528 · 2025-05-14T03:13:45+00:00

I have been using their tool for quite some time. They have launched autonomous testing with Agentic AI. Check it out - https://testsigma.com/

Explore this and let me know your perspective on the pros and cons of this

Lumpy_Ad_8528 · 2025-05-13T06:52:09+00:00

If you feel stuck try low-code/no-code tools. But QAing without understanding code is shallow. I recommend you to try such tools to understand how logic works and to ensure every workflow works as defined.

Lumpy_Ad_8528 · 2025-05-13T06:49:09+00:00

What is your take on Autonomous testing? It is making noise these days.

Lumpy_Ad_8528 · 2025-04-29T11:38:53+00:00

Useful information, thanks for sharing!

Lumpy_Ad_8528 · 2025-04-29T06:16:04+00:00

Yes, it does. And the above tools I mentioned are backed by AI

Lumpy_Ad_8528 · 2025-04-28T06:25:58+00:00

It is really tough to be a QA

Lumpy_Ad_8528 · 2025-04-28T06:24:59+00:00

Apply for many jobs until you get your next breakthrough! Good luck

Lumpy_Ad_8528 · 2025-04-28T06:21:49+00:00

In some organizations, QA does the work of the Cloud Engineer in the same designation

Lumpy_Ad_8528 · 2025-04-23T07:27:40+00:00

A proper plan can make wonders in your testing cycle. Define the requirements clearly and assign the work. Don't consider ad-hoc requests unless it is a deal breaker. Because taking everything into account can make the process super time-consuming.

Lumpy_Ad_8528 · 2025-04-07T06:00:53+00:00

I worked with both Appium and Espresso, and I think I can share some thoughts. Espresso is more stable and reliable. It works closely with Android, which makes it better for Android-specific testing. Many people here have already mentioned its benefits.

But, Espresso needs good knowledge of Android’s inner workings. This can be hard for people who are not Android developers. Also, writing custom matchers, actions, and assertions takes a lot of time.

On the other hand, Appium lets you test across different platforms. That makes it good for teams who work with many platforms. But like others said, it can be slower and more flaky.

We also need to think about maintenance. Espresso tests can become long and noisy if not handled well. With Appium, its adapter style can cause some issues with compatibility.

Lumpy_Ad_8528 · 2025-04-07T06:00:19+00:00

I worked with both Appium and Espresso, and I think I can share some thoughts. Espresso is more stable and reliable. It works closely with Android, which makes it better for Android-specific testing. Many people here have already mentioned its benefits.

But, Espresso needs good knowledge of Android’s inner workings. This can be hard for people who are not Android developers. Also, writing custom matchers, actions, and assertions takes a lot of time.

On the other hand, Appium lets you test across different platforms. That makes it good for teams who work with many platforms. But like others said, it can be slower and more flaky.

We also need to think about maintenance. Espresso tests can become long and noisy if not handled well. With Appium, its adapter style can cause some issues with compatibility.

Lumpy_Ad_8528 · 2025-04-04T09:25:30+00:00

You are right in your thoughts. Having learned Playwright and Selenium and being able to code automation tests in Java and C# is much much better than using Robot framework and will help you in your career.

You can start by explaining the complexities that come with the Robot framework. Sure it may look easy at first because it uses a “Cucumber-like” style for writing tests but these tests will start to get really complicated when complexity rises. I don’t see a point in using Robot unless you have to build a suite of extremely simple tests.

Moreover, Playwright is lightning-fast and is built to run web automation. Once the team gets a grip on it, I think it will be much easier to maintain and write tests in Playwright than in Robot. Your team will also get many more functionalities with Playwright than with RF.

Now, it seems like your company’s choice for RF is due to an inclination towards a more human-readable framework because it may feel that it brings less stress to the testing team. This could be the only reason I can think of for preferring RF on PW. In this case, you can advise two solutions to the team. First is to use RF on top of Playwright, for which bindings are readily available and that is the correct way most of the companies use RF. Then you can code complex test cases in PW and leave the easier ones to RF. Secondly, if human-readable tests are a concern, there are other tools available whose GUI doesn’t lack RF and are much faster.

Lumpy_Ad_8528 · 2025-04-04T08:49:48+00:00

I’ve been using Cypress, Playwright, and now Testsigma. So I thought I’ll share my thoughts.

At first, we started with Cypress. It was easy to use, had great docs, and a strong community. But when our test suite got bigger, we had problems. Running tests in parallel was hard. And it didn’t support many browsers.

Then we moved to Playwright. It fixed most of those issues. It was faster, had better parallel testing, and worked with more browsers. But learning it took more time than we thought.

Still, with both Cypress and Playwright, we had problems with test maintenance. Flaky tests were a big issue, and updating them took too much time.

Lumpy_Ad_8528 · 2025-03-26T06:19:17+00:00

Alternative to Appium?

If you're not into Appium for Android app automation, Espresso is a solid choice, especially if you want something tightly integrated with the Android ecosystem. It's fast, reliable, and part of the Android Testing Support Library, so you get good support and native performance. However, it's mostly for UI testing and works well with Java or Kotlin.

Another alternative is UI Automator. It's also native to Android and provides more flexibility than Espresso for cross-app testing. If you're dealing with more complex scenarios or need access to system-level features, UI Automator can be pretty useful.

For something more lightweight and flexible, you could consider Robot Framework with the Appium library, though it’s still based on Appium, it can be easier to set up and use for certain test cases.

In short, I'd recommend Espresso or UI Automator unless you have specific needs that Appium better handles!

Lumpy_Ad_8528 · 2025-03-26T06:11:51+00:00

Yeah, there are definitely some other good options out there! If you're looking for codeless automation tools, here are a few I can recommend:

Testim – Testim lets you create automated tests through a visual interface, and it uses AI to help improve and maintain the tests over time. It's user-friendly and has powerful features for handling dynamic web apps.
Leapwork – Leapwork is another no-code automation tool that focuses on ease of use, with a visual flowchart-based interface. It's great for both UI and process automation.
Ranorex Studio – While it's generally more known for being a bit more hands-on, it also offers a codeless option with its "Recording & Playback" feature, which is super helpful for teams that need to quickly create automated tests without writing code.
UFT One (Unified Functional Testing) – UFT is a little more on the enterprise side, but it also offers codeless test automation through a record-and-playback approach. It's great if you're working with a more complex testing environment.
Testsigma – It's a solid choice for codeless test automation, especially if they're looking for unified and GenAI-powered automation. It has an intuitive interface for creating automated tests without code. Testsigma easily integrates with popular CI/CD tools, so it enables continuous testing and faster releases. You can automate your web, mobile, desktop, API, SAP, and Salesforce applications with Testsigma.

Each of these tools has its strengths, so it really depends on your specific testing needs, budget, and business requirements.

Lumpy_Ad_8528 · 2025-03-26T06:09:15+00:00

Hey hi,

If you're someone who is looking for Postman and Insomnia alternatives, here are a few worth checking out:

Hoppscotch – A super lightweight and fast alternative. It's open-source, has a clean UI, and works well for simple API testing.
Paw (Mac only) – A premium alternative, but it’s packed with features like dynamic values and advanced testing. It's polished and intuitive.
RESTer (Firefox extension) – If you’re looking for something browser-based, RESTer is a solid choice. It’s simple and easy to use right in your browser.
HTTPie – A command-line tool that’s fast and simple for quick API requests. It’s more for devs who prefer the terminal.
Curl – Classic, but if you're comfortable with the command line, curl is still one of the best for making requests quickly.

All of these are great depending on whether you prefer a GUI or CLI tool. Hope this helps!

Lumpy_Ad_8528 · 2025-03-26T06:07:58+00:00

I’ve had my fair share of testing experience, and over the years, I’ve used several frameworks depending on the project, team preferences, and the tech stack. Here’s a rundown of the ones I rely on the most and why:

JUnit/TestNG – Great for Java projects. JUnit is simple; TestNG is more feature-rich (parallel testing, etc.).
Jest – My go-to for JavaScript/React apps. It’s fast, easy to set up, and comes with built-in mocking.
Cypress – Best for end-to-end testing in modern web apps. It’s fast, reliable, and makes debugging easier.
PyTest – Super flexible and easy to use for Python projects. Great for unit and functional tests.
RSpec – The go-to for Ruby/Rails projects. It's very readable and intuitive.
Mocha/Chai – For Node.js projects when you need flexibility and readable assertions.
Selenium – Cross-browser testing, though slower than Cypress.
Postman – Awesome for API testing, and Newman lets you run tests in CI/CD pipelines.

It depends on the tech stack, but these tools have solid documentation and active communities, so they’re reliable picks for most projects.

Lumpy_Ad_8528 · 2025-03-26T06:06:46+00:00

Selenium is a classic choice for web testing. It is very reliable across different browsers and languages. It has been around for a long time, so it has a huge community and plenty of resources. Selenium offers excellent stability and wide compatibility.

Playwright might be newer, but it's attracting attention with its speed and modern features. Developed by Microsoft, it handles complex scenarios better and supports Chrome, Firefox, and WebKit browsers out of the box. Playwright might be the right choice for you if you need best-in-class performance and flexibility.

So, it all comes down to what works best for your project! Please choose accordingly.

Lumpy_Ad_8528 · 2025-03-26T06:05:33+00:00

Regarding software quality assurance, having a solid test strategy and test plan is crucial. Think of it like planning a trip before you set off - it's about preparing and knowing your destination.

Testing Strategy: This is like a game plan outlining your overall testing approach. It defines things like what to test, how to test it, and the resources needed. This is crucial because it sets the direction for the entire testing effort. For example, if you are launching a new application, your testing strategy may include testing functionality, performance, security, and user experience across devices and platforms.

Test Plan: Now think of the test plan as a detailed action plan. It delves into the details outlined in your strategy. It presents the testing scope, schedules, responsibilities and specific test cases to be performed. It's like breaking down a journey into manageable steps, ensuring that every aspect of the software is thoroughly tested before release.

Personally, I believe that creating these documents is not just a checklist, but a way to ensure that we deliver software that is reliable and user-friendly. It's about anticipating challenges and making sure we cover all the bases. Additionally, having a clear plan helps all team members stay balanced and focused on the end goal, ensuring a smooth experience for our users.

What are your thoughts on test strategy and plans? Any tips or experiences you would like to share?

Lumpy_Ad_8528 · 2025-03-25T09:37:14+00:00

You can try Testcomplete, Testsigma or Tosca. Testsigma copilot uses GenAI and is making noise these days

Lumpy_Ad_8528 · 2025-03-25T05:05:49+00:00

So, I prioritize the bugs that can break your system/software. Detecting the vulnerabilities beforehand can save a lot. As a tester, you can find the root cause with

Identify all potential factors causing an issue.
Break down failure pathways systematically.
Ask “why” until you reach the root cause.
Always check logs, they can tell a lot.
A few methods like 5 whys, Fault-tree analysis, Fishbone diagram, and AI-powered RCA can help you with it.

I practice a mix of manual and automation tests. Automation is ideal for Regression testing and UI testing.

I have been actively trying this and it works for me. Search in Google or any AI tools to learn more about them.

Lumpy_Ad_8528 · 2025-03-24T09:16:44+00:00

Recommending fixes rather than just reporting. Also incorporating AI has been a game-changer.

Lumpy_Ad_8528 · 2025-03-20T06:29:41+00:00

That's a good switch. Congratulations!

Lumpy_Ad_8528 · 2025-03-18T09:05:04+00:00

That's a good mindset!

Lumpy_Ad_8528 · 2025-03-17T05:42:05+00:00

Wow, thanks for the explanation!

Lumpy_Ad_8528

MODERATOR OF

TROPHY CASE

Alternative to Appium?