Dipak Bist Software QA Engineer

I have 4+ years of experience testing web applications and multi-tenant SaaS platforms — designing risk-based test suites, automating regression paths with Playwright and Python, and verifying REST APIs with Postman.

test_login.py

ready
import os

import pytest
from playwright.sync_api import Page, expect


@pytest.fixture(autouse=True)
def setup(page: Page):
    page.goto("https://app.example.com")


def test_login(page: Page):
    page.get_by_label("Email").fill(os.environ["USER_EMAIL"])
    page.get_by_label("Password").fill(os.environ["USER_PASSWORD"])
    page.get_by_role("button", name="Sign in").click()
    expect(page).to_have_title("Dashboard")

pytest -v test_login.py

test_login.py::test_login[chromium] PASSED [100%]

About Me

Dipak Bist, Software QA Engineer, Kathmandu
  • 4+ Years Experience
  • Kathmandu, Nepal
  • Open to Opportunities

I am a Software Quality Assurance Engineer with over four years of experience in software testing, test automation and quality engineering, specialising in web applications, mobile applications and SaaS platforms. I focus on building reliable testing strategies, developing scalable automation frameworks and improving software quality throughout the Software Development Life Cycle (SDLC).

Currently, I work at Sterling Wells on FigsFlow, a multi-tenant SaaS platform designed for accountancy firms. My responsibilities involve validating complex end-to-end business workflows, including client onboarding, AML and risk assessments, proposal and engagement generation, user roles and permissions, subscription management, billing, document generation and third-party integrations. Working with complex SaaS architecture has strengthened my understanding of business logic, data integrity, access control and tenant-level data isolation.

My technical expertise covers Manual Testing, Test Automation, API Testing, Performance Testing and End-to-End Testing. I design and maintain automation frameworks using Playwright with Python, applying Page Object Model (POM) and Behaviour-Driven Development (BDD) principles to build maintainable, reusable and reliable automated test suites. I also use Postman for REST API testing and Apache JMeter for performance and load testing, alongside database validation, log analysis and integration testing.

Read the full story

A key area of my professional development is AI-driven Quality Engineering. I leverage tools such as Claude Code to accelerate test case generation, develop and optimise automation scripts, analyse test failures, investigate defects and improve QA documentation. I also work with AI-assisted workflows integrating Claude with Azure DevOps Boards to streamline test management, bug reporting, work item creation and QA reporting. I am particularly interested in leveraging Model Context Protocol (MCP) to connect AI assistants with testing tools and development environments, creating more intelligent and efficient QA workflows.

Beyond technical testing, I take a risk-based approach to quality assurance, analysing requirements, identifying potential failure points and prioritising test coverage based on business impact. I collaborate closely with developers, product managers and stakeholders in Agile Scrum environments, contributing to test planning, defect management, sprint activities, release validation and continuous quality improvement.

I believe quality engineering goes beyond identifying defects. It is about preventing issues, improving development processes, building confidence in software releases and delivering reliable products that create real value for users.

I am continuously expanding my expertise in AI-powered testing, advanced automation architecture, CI/CD integration, API automation and modern Quality Engineering practices.

My Quality Engineering Workflow

0/10 steps

Ten steps, in the order they happen on a real ticket. Each one ticks as you reach it.

  1. Plan

    Requirements

    I read the requirement before the ticket, and write down what is ambiguous.

  2. Risk analysis

    Which failures would cost the most? That ranking decides where the effort goes.

  3. Test planning

    Scenarios and cases mapped back to requirements, so coverage is arguable.

  4. Test

    Manual testing

    Exploratory passes first — scripted cases only find what they were written for.

  5. API validation

    Contract, auth and error paths checked at the service layer before the UI.

  6. Automation

    Regression-critical journeys move into Playwright so they run every time.

  7. Performance

    JMeter against the paths that carry load, watching where latency turns.

  8. Release

    Regression

    The automated suite runs on every change; failures are triaged, not muted.

  9. Release validation

    UAT and a smoke pass against the release build before sign-off.

  10. Learn

    Continuous improvement

    Every escaped defect becomes a new case and a question about why.

Then back to 01, Requirements: the loop starts again.

Professional Experience

  1. Feb 2024 – PresentCurrent

    Associate QA Engineer

    Sterling Wells · Product: FigsFlow

    • Test Automation Engineering: Design, develop and maintain scalable end-to-end test automation frameworks using Playwright with Python, following the Page Object Model (POM) design pattern to ensure maintainability, reusability and reliability.
    • AI-Assisted QA Engineering: Leverage Claude Code and AI-powered development workflows to accelerate test case generation, automation script development, test debugging, failure analysis, code reviews and overall QA productivity.
    • AI-Driven QA Workflow Integration: Integrate Azure DevOps Boards with Claude-powered workflows to streamline QA operations, including work item creation, bug reporting, test documentation, ticket analysis, status updates and QA reporting.
    • MCP-Enabled Testing Workflows: Explore and utilise Model Context Protocol (MCP) integrations to connect AI assistants with testing tools, development environments and project management systems, enabling context-aware QA workflows and improved testing efficiency.
    • API Testing: Design and execute REST API tests using Postman collections, validating endpoint functionality, request/response structures, status codes, data integrity and integration behaviour.
    • Test Planning & Strategy: Develop comprehensive test plans, test scenarios, test cases, regression strategies and risk-based testing approaches to ensure adequate functional and business requirement coverage.
    • Comprehensive Software Testing: Perform functional, regression, smoke, integration, end-to-end, User Acceptance Testing (UAT) and exploratory testing across FigsFlow modules and workflows.
    • Defect Management: Identify, document, prioritise and track defects in Jira and Azure DevOps, providing clear reproduction steps, expected versus actual results, supporting evidence and regression verification.
    • AI-Powered QA Productivity: Apply AI tools to improve test coverage, analyse application behaviour, identify potential edge cases, generate test data, investigate failures and optimise repetitive QA activities.
    • Agile Collaboration: Work closely with developers, product stakeholders and QA team members in an Agile Scrum environment, participating in sprint activities, requirement analysis, defect triage and release validation.
    • QA Mentoring & Knowledge Sharing: Mentor junior QA engineers in manual testing, test design techniques, automation fundamentals, defect reporting, testing best practices and Agile QA processes.
  2. Aug 2023 – Feb 2024

    QA Analyst

    E-Signature Pvt. Ltd.

    • Test Documentation & Planning: Developed comprehensive test documentation for each software release based on functional requirements, including test plans, test scenarios, test cases and test execution reports to ensure systematic test coverage.
    • Release Testing & Validation: Managed end-to-end release testing activities, performing smoke, functional, regression and User Acceptance Testing (UAT) to validate application quality and release readiness.
    • Defect Management & Collaboration: Identified, documented and tracked software defects using Jira, providing clear reproduction steps and expected versus actual results while collaborating with developers to verify fixes and ensure successful resolution.
    • Quality Assurance & Reporting: Prepared and communicated test execution results, defect summaries and release validation reports to provide stakeholders with clear visibility into software quality and testing progress.
  3. Mar 2023 – Aug 2023

    Quality Assurance Intern

    Moru Digital Wallet

    • Web & Mobile Application Testing: Performed comprehensive manual testing of web and mobile applications against business requirements, validating functionality, usability, compatibility and application behaviour across different platforms and devices.
    • Test Case Design & Execution: Prepared, reviewed and executed test cases for assigned features, covering functional scenarios, positive and negative test cases, edge cases and business requirements.
    • UI/UX Testing: Evaluated user interface and user experience across web and mobile applications, ensuring layout consistency, responsive design, intuitive navigation and seamless user interactions.
    • Agile Team Collaboration: Actively participated in Agile Scrum ceremonies, including sprint planning, daily stand-ups, sprint reviews and defect triage, collaborating with team members to maintain product quality and support timely issue resolution.

Skills & Expertise

  • Manual & Functional Testing

    Core

    I own the manual coverage for a platform that accountancy practices run their client work through. The judgement call is where to go deep and where a quick check is enough.

    • Risk-based test design — I rank features by how much damage a failure does, and test the expensive ones hardest
    • Charter-driven exploratory sessions, to catch what scripted cases never look for
    • Requirement-to-test traceability, so I can show which case covers which requirement
  • Test Automation

    Core

    Playwright with Python is my primary stack, and Selenium with Behave covers my earlier BDD work. I lean on fixtures and shared selectors so a suite stays cheap to maintain as the product moves.

    • Pytest fixtures for setup, teardown and pre-authenticated sessions
    • One source of truth for selectors, so a UI change is a one-line fix
    • Allure reporting, and the same suite run across Chromium, Firefox and WebKit
  • API Testing

    Core

    I work at the service layer as well as in the browser. In practice that means Postman collections per environment, plus Python Requests for the checks I want living inside the automated suite.

    • Auth and refresh-token flows, including expiry and re-issue
    • Status code, header and JSON Schema response validation
    • Environment-driven runs, so one collection covers dev and staging
  • Test Management & Agile QA

    Core

    I keep the QA side of a Scrum team legible — what is under test, what is blocked and what is ready. Defects live in Jira or Azure DevOps Boards depending on the project.

    • Defects triaged, prioritised and driven through to verified, not just logged
    • I take the QA slot in refinement so testability is agreed before build starts
    • Confluence for test documentation the rest of the team can actually find
  • Performance Testing

    Growing

    The area I am actively building. I use JMeter to find where response times start to degrade, rather than assuming a page is fast because it feels fast on my machine.

    • Load and spike scenarios modelled on realistic concurrent usage
    • Response time, throughput and error-rate analysis
    • Reports that show where the ceiling actually is
  • Databases & Version Control

    Working

    I use SQL to confirm that what the interface claims actually reached the database, and I work in Git the same way the developers on my team do.

    • SQL queries to check a workflow wrote what it was supposed to write
    • Feature branches for automation work, merged through pull request
    • Code review on test code, in both directions

How I Use AI in Quality Engineering

I integrate AI into my Quality Engineering workflow to improve efficiency, accelerate test development and streamline repetitive QA activities. I use Claude Code as an engineering assistant across test design, automation development, debugging and QA documentation.

My approach is built around human oversight and engineering judgement. AI helps accelerate implementation, explore scenarios and reduce repetitive work, while I remain responsible for test strategy, risk assessment, technical decisions and quality validation.

Every AI-generated output is critically reviewed, validated against business requirements and refined before being introduced into the automation framework or project workflow. AI supports my engineering process; it does not replace the reasoning behind it.

How I Apply AI

  • Intelligent Test Case Generation

    Use Claude Code to analyse functional requirements, explore edge cases, identify negative scenarios and generate structured test cases. Review and refine scenarios to ensure meaningful coverage and alignment with business logic.

  • Test Automation Development

    Leverage AI to scaffold Playwright automation scripts, Page Object Model (POM) classes, reusable components, fixtures and test utilities. Review generated code for maintainability, reliability and framework consistency.

  • Automated Failure Analysis & Debugging

    Use AI to analyse test failures, stack traces, execution logs and application behaviour to investigate potential root causes, accelerate debugging and reduce troubleshooting time.

  • AI-Assisted Code Review

    Use Claude Code as a secondary review assistant to identify potential code issues, improve test structure, detect duplication and assess automation quality before changes are integrated into the framework.

  • Azure DevOps & MCP Integration

    Connect Claude Code with Azure DevOps Boards through MCP-based workflows to streamline work item creation, defect reporting, task management and QA reporting. Use existing board context to generate structured tickets and reports, with human review before submission.

Projects

  • API Testing

    REST API Testing Framework

    A reusable framework for testing REST services in Python. It exercises sign-in and token renewal, validates response bodies against a schema instead of eyeballing them, and reads its base URL and credentials from configuration so a single suite serves every environment. Postman collections cover the exploratory work alongside it.

    • Python
    • Requests
    • JSON Schema
    • Postman

    Repository not public yet

  • Fintech

    Digital Wallet QA (Mobile & Web)

    Hands-on QA for a digital wallet, covering both the mobile app and the web side. I wrote and ran the functional cases, checked the interface against the designs at several screen sizes, and joined the triage sessions where incoming defects were prioritised. All manual work — no automation on this one.

    • Manual QA
    • Mobile
    • Web
    • Jira

    Internal work, no public link

  • BDD

    BDD Test Framework

    Selenium, Python and Behave driving the Swag Labs demo shop. Feature files describe the behaviour in plain language, step definitions do the driving, and each run leaves a report behind. It is the shape I would use to make acceptance criteria executable on a real product.

    • Selenium
    • Python
    • Behave
    • Gherkin
  • CommunityFounder · Community organisation

    Dreamer's Youth Club

    I founded Dreamer's Youth Club, a community organisation in Kanchanpur working on youth civic engagement, education and community action — and I built and maintain its website. It is a vibe-coded React build: I set the structure, content and design direction, leaned on AI for the implementation, and did the cross-device and accessibility checks myself before it went live.

    • React
    • Vibe-coded
    • Responsive
    • SEO

From the Blog

  1. How to Write a Good Bug Report: The Complete QA Guide

    A vague bug report gets ignored. A precise one gets fixed the same day.

    QA Fundamentals
  2. Playwright API Testing Guide: Test REST APIs Without a Browser

    Playwright is not only for driving browsers — its request layer makes fast, reliable REST tests.

    Python
  3. Manual Testing vs Automation Testing: When to Use Which

    The real strengths and trade-offs of each, and a practical way to decide.

    Test Strategy

View all posts

Get in Touch

I am open to QA roles, remote or Kathmandu-based. If you want to talk about testing on your product, I would like to hear from you.

Or copy my address directly:

Send a message