This publication is a place for testers, QA engineers, developers and quality leaders to share what they’ve learned from their work.

We welcome stories from everyone: BrowserStack’s own experts, and anyone in the testing community who doesn’t work at BrowserStack. You don’t need to be a professional writer, just someone with real experience to share.

Who we’d love to hear from

We’ll save you the guesswork. We’re looking for:

• QA engineers, SDETs and testers
• Developers who care about quality
• Test automation and DevOps engineers
• AI testing experts, whether using AI to test or testing AI-powered applications
• Accessibility specialists
• QA and engineering leaders

If you don’t see your role here but you write about testing, reach out anyway.

What we publish

The stories we love most come from real work. Here are some examples:

• A tutorial or how-to based on something you’ve actually built
• A write-up of a technical problem your team solved, and how
• A framework or tool comparison from hands-on use
• How you set up a test pipeline, environment or process
• How you’re using AI in testing, and what you’ve learned
• Your perspective on QA strategy, team practices or quality culture

A few things aren’t a fit for us: general programming content unrelated to testing, listicles without original insight, press releases, and content written mainly to promote a product or service.

What makes a story stand out

Here’s what our editors look for:

• It’s original. We welcome new stories, as well as stories you’ve already published on your own Medium profile. We don’t accept stories published on other sites, such as a personal blog, Dev.to or LinkedIn.
• It’s grounded in experience. Show your work such as the steps, code, configurations, screenshots or results.
• The headline says what readers get. Be direct and straight to the point. If you have any metrics“How we cut our regression suite from 4 hours to 40 minutes” beats “Speeding up tests” every time.
• It gets to the point. Share your main takeaway in the first paragraph.
• It’s easy to scan. Use subheadings, short paragraphs, and code blocks for code.
• It’s accurate. Link to sources for any data, benchmarks or claims about tools.

A note on tools, including ours

Mention any tools that are relevant to your story. Explain how a tool helped solve the problem rather than only listing features, keep comparisons fair and factual, and please refrain from using promotional language and links.

A note on using AI

We value the effective use of AI in research and writing, but we strongly discourage content created only with AI.

Your thoughts, examples, edge cases and recommendations must be 100% original and drawn from your own experience. Please make sure every fact and code samples is checked before you hit publish.

Being transparent

• If you work at BrowserStack, please mention it in your Medium bio, for example “QA Engineer at BrowserStack”.
• If you’re writing about a product you build, sell or are paid by, say so in the story.

Before you hit submit, here’s a quick checklist

• Title and subtitle
• Add 5 relevant tags (for example: Software Testing, Test Automation, Quality Assurance, Selenium, Accessibility)
• A cover image that you have the rights to use with credits wherever it’s due
• Alt text on every image
• Code formatted in code blocks
• Links to any sources you reference

How to submit

First, get added as a writer. Share your Medium username through this form. An editor will add you to the publication within two working days.

Submitting a new story:

1. Write your story as a draft on Medium. Don’t publish it on your own profile first.
2. Open your draft, click the “…” menu and select “Add to publication”.
3. Choose BrowserStack and submit.

Submitting a story already on your Medium profile:

1. Open the published story.
2. Click the “…” menu and select “Add to publication”.
3. Choose BrowserStack and submit. Once accepted, it moves into the publication, and the link to your original post will still work.

What happens next

Our editors review every submission within four working days. We may suggest edits or ask for a few changes before publishing. Not every story will be the right fit; if yours isn’t, we’ll let you know and, where we can, tell you why.

Once your story is live, it stays under your name, and you’re welcome to share it anywhere.

Questions?

Reach us at editorial@browserstack.com

We can’t wait to read what you write.

— The BrowserStack Medium Editorial Team

Write for BrowserStack on Medium was originally published in BrowserStack on Medium, where people are continuing the conversation by highlighting and responding to this story.

Welcome to BrowserStack’s new publication on Medium.

We have learnt over the years that the most useful lessons in software testing sometimes do not make it into your regular documentation. You will find them in zoom recordings of debugging sessions, team retros, and long slack threads.

This publication is aimed to bring these lessons out into the open.

A Quick Recap About BrowserStack

Here’s the short version:

• BrowserStack is the testing platform for web and mobile apps, with AI at every step of the testing lifecycle.
• More than 50,000 customers in 135+ countries and over 7 million developers use it to test on real browsers and devices.

Working with so many teams, we see every day how differently people approach quality, and how much they can learn from each other.

What you’ll read here

Stories behind good testing: hands-on fixes, honest lessons and the ideas changing how teams build quality software.

Written by people who do the work, from BrowserStack and across the testing community.

We Want to Hear You

If you’ve solved a hard testing problem or have a perspective worth sharing, we’d love to publish it.

Follow the publication to get new stories every week. And reply below: what testing topic do you want us to cover first?

Thanks for reading! We’re looking forward to learning alongside you.

— The BrowserStack team

Welcome to BrowserStack on Medium was originally published in BrowserStack on Medium, where people are continuing the conversation by highlighting and responding to this story.