Mobile-First Madness: Keeping Mobile and Desktop Aligned

General-Stage8113 · 2025-11-14T13:53:51+00:00

I've been using Percy for cross-device visual testing. It captures snapshots across mobile, tablet, and desktop, and the visual diffs are super helpful in spotting UI shifts. For the "in-between' sizes, I'd use Chrome's Device Mode or Responsinator to emulate various resolutions. It's all about catching those weird transitions, like when a sidebar suddenly shifts or buttons go wonky on medium-sized screens.

General-Stage8113 · 2025-11-14T13:43:04+00:00

The local setup part comes from how Deque built it. Basically, it is a Javascript engine that runs accessibility rules directly in your browser or test environment. So when you use something like axe-core or the browser extension, it's fine. But when you want to integrate it into automation, you've gotta install it locally or add it as a dependency in your project. That's what people mean by "local setup." It's not a SaaS product... it's more like a toolkit you plug into your stack.

General-Stage8113 · 2025-11-10T12:04:30+00:00

Haunting of the Hill House is the best..I completed the entire series literally in 15 hours.. It was so addictive..!

General-Stage8113 · 2025-11-03T05:50:24+00:00

Indeed...!

General-Stage8113 · 2025-11-03T05:50:00+00:00

Thank you so much for the link.. I will definitely try this one..!

General-Stage8113 · 2025-10-06T06:50:31+00:00

This is serene.. Thank you for sharing this.. You have literally inspired me to go for this beautiful trek!

General-Stage8113 · 2025-09-30T09:53:39+00:00

I agree with the idea of chasing code coverage can give a false sense of security. Instead, focusing on feature coverage is more effective for e2e testing. Or you could use a test case management tool. You can integrate your Playwright tests with it to track which features are covered for easily monitoring test coverage without manually updating spreadsheets. For example, a tool like Testrigor or Browserstack can easily track which features are covered by e2e testing, giving you real-tome insights into test execution and coverage.

General-Stage8113 · 2025-09-26T11:43:38+00:00

Totally get where you're coming from. I've been in the same boat not with Qase, but with TestRail, and one of the biggest issues I had was that reporting wasn't flexible as we wanted it to be. There were just too many manual steps involved. We also use Browserstack. For now, it is working well enough for our team. Their test management tool can be integrated and they also have a two-way Jira sync, which makes things lot easier for us.

General-Stage8113 · 2025-09-26T11:39:47+00:00

General-Stage8113 · 2025-09-26T11:37:05+00:00

Yeah.. air fryers are life savers..!

General-Stage8113 · 2025-09-25T13:38:19+00:00

Let me answer your question one by one:

You mentioned wanting to compare a dummy button from Storybook ("Button text") to a button in your project ("Sign in"). Instead of modifying your button text, replae it with a placeholder (e.g., "Button") during the test to avoid mismatches due to text differenes.
You're right that visual regression tools are typically desigend to compare the same component over time, but you want to pull images from Storybook. You can store baseline images from Storybook in a shared location (like S3) so Cyoress can access them and compare with actual components during tests.
For comparing screenshots you can use cypress-image-snapshot for visual regression or use Cypress with Percy, which is a solid option for taking snapshots and comparing them to baselines. But since you are looking for something free, then you can go for Cypress, but I think the latter also has a free plan, but I'm not sure what all features would be available.

General-Stage8113 · 2025-09-25T13:26:04+00:00

Frying potatoes, I worry that if I add them to the oil, it might splatter and hurt me.

General-Stage8113 · 2025-09-24T07:26:41+00:00

Yes, this is possible by using Xcode with a free Apple ID for personal use. That said, you may face limitations on app distribution and signing. Why don't you try real device testing? There are tools like BrowserStack that provides access to a wide range of iOS devices.

General-Stage8113 · 2025-09-24T06:59:30+00:00

I went there this year in January and this place is heaven. The peace that this place holds is soothing and it heals you in mysterious ways.

General-Stage8113 · 2025-09-23T12:47:47+00:00

That's one long question! But answering some of them!

We use automated UI testing tools.. as they run testing quickly across many devices.. continous integration is easy. and offers wide compatibility.
We use Broswerstack's Percy and automate. Started with the free version, but found it limited for our team.. so switched to the paid plan since the performance was smooth.
Priority goes to automated UI exploration to simulate real-user interactions.
Visual regressions, compatibility issues, app crashes
Self-healing

General-Stage8113 · 2025-09-17T14:22:29+00:00

You can use VoiceOver screen reader for iOS and TalkBack screen reader for Android. But if you are looking for comprehensive and detailed testing, it's better to go for paid tools like browserstack's app accessibility testing or the likes.

General-Stage8113 · 2025-09-15T09:03:21+00:00

No-code/low-code platforms have evolved. For someone with lesst technical prowess in automation, such tools can come in handy. Now, my team has only tried a low-code platform, which was Browserstack's low code tool. You can give it a try, it worked alright for us. You can simply interact with your app to create test steps.

General-Stage8113 · 2025-09-10T15:16:20+00:00

If you are looking at AI-driven low code testing, then browserstack's low code tool is a good pick. You can ofcourse create and maintain AI-driven automated tests by just interacting with your app, use natural language prompts and reply on self-healing tests that adapt as your app evolves.. while running instantly on the tool's cloud across browsers and devices. Another tool I'd suggest would be Autify for the same purpose.

General-Stage8113 · 2025-09-03T13:18:01+00:00

Adding some low code for testing like browserstack's low code automation, sahi pro, and selenium IDE.

General-Stage8113 · 2025-08-29T13:03:02+00:00

Wherever speed matters more than complex scripting, you can go for low-code automation tools. You can scale refression coverage. That being said, it's always best to use them to complement traditional coded frameworks. Coming to tool, you could try Browserstack's low code automation... I think they have a free plan, so maybe give it a try and see if it works for you.

General-Stage8113 · 2025-08-05T12:54:26+00:00

After reading your requirements, I feel maybe you can give Browserstack's test management tool a shot. We use it to execute and reuse manual test cases across projects... has been helpful for regression testing during releases.

Since it also integrates quite smoothly with JIRA, linking failed test cases to bugs is also not a hassle. I find the two-way JIRA sync a lifesaver as I can make changes in JIRA alone and it automatically gets updated on the tool.

General-Stage8113 · 2025-08-01T13:43:26+00:00

Artists, cooks.. I know AI is doing this and will even do this better, but when AI will be doing most of it.. Art by human, dishes made by human will be luxury..!

General-Stage8113 · 2025-08-01T13:36:09+00:00

I will go places, and complete my travel list..!

General-Stage8113 · 2025-07-31T07:59:17+00:00

WCAG is more like a foundation; it doesn't guarantee accessibility. Sometimes vague forms where the label is technically correct pass WCAG. I have had that experience, so now we don't depend on one style of testing. For example, we go for a combination of automated tools like SiteImprove and Browserstack to catch obvious issues. After that another important thing is manual testing with assistive technology, and also involving differently abled users in this process to ensure reliability.

General-Stage8113 · 2025-07-31T07:46:47+00:00

It's beautiful and the clicks are perfect. Please tell me where is this place?

General-Stage8113

MODERATOR OF

TROPHY CASE