Tester

Run comprehensive pre-release testing across UI/UX, code, security, and CI/CD readiness.

18|3|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/SaadhJawwadh/Note-taking --skill tester-saadhjawwadh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tester
Source: https://github.com/SaadhJawwadh/Note-taking/tree/main/.agent/skills/Tester
Command: npx skills add https://github.com/SaadhJawwadh/Note-taking --skill tester-saadhjawwadh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of shipping broken or insecure app changes by driving comprehensive, structured testing across quality, security, and release workflows.

Core Features & Use Cases

  • UI/UX consistency testing: Validate usability, accessibility, and adherence to Material Tree Expressive Design, including multi-view layout persistence and widget interactions.
  • Codebase QA with critical audits: Systematically uncover logic bugs and enforce backup completeness and settings restore correctness by checking specific implementation patterns.
  • Security and privacy auditing: Look for vulnerabilities such as encryption flaws, exposed secrets, and unsafe data handling.
  • CI/CD release readiness: Ensure build and release workflows are consistent (e.g., JVM 17 targets), ProGuard integrity, Play Store artifact production, and migration safety.

Quick Start

Use the Tester skill to run a full release readiness checklist for your next update, including the required backup completeness and settings restore audits.

Frequently Asked Questions about Tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is release-ready QA for Android CI/CD and database migrations?

Release-ready QA systematically verifies UI/UX consistency, code correctness, security, and deployment pipeline readiness. It requires sequential phase execution to ensure Android builds pass JVM 17 targets, ProGuard keep rules, and safe database migrations before Play Store release.

How do I audit backup completeness and settings restore correctness in my app?

To audit backup and settings restore, systematically check specific implementation patterns for logic bugs and enforce backup completeness. This structured testing validates that note-taking features and settings flows correctly persist and restore data across app updates.

Does this testing workflow check for security vulnerabilities like encryption flaws and exposed secrets?

Yes, security and privacy auditing identifies encryption flaws, exposed secrets, and unsafe data handling. It reviews privacy implementations to ensure sensitive user data remains protected throughout note-taking features and settings backup flows.

How do I validate UI accessibility and Material Design consistency across multiple views?

UI/UX consistency testing validates usability, accessibility, and adherence to Material Tree Expressive Design. It checks multi-view layout persistence and widget interactions to ensure interfaces remain consistent and accessible across different app states.

Can I use this QA checklist to verify Play Store artifact production and ProGuard integrity?

Yes, CI/CD release readiness verification enforces ProGuard keep rules, JVM 17 targets, and Play Store artifact production. It ensures build and release workflows remain consistent and deployment-ready for Android applications.

What are the limitations of running pre-release verification for Android database migrations?

Pre-release verification requires sequential phase execution, meaning migration safety checks must follow strict ordering. You cannot skip the explicit backup and restore audits, as these phases validate critical data integrity before deployment.