TestDino avatar

TestDino

Official

@testdino-hq · United States of America

0Followers
|
18Public Repos
|
24Published Skills

Smart playwright test reporting platform

Skills Distribution
DomainDeveloper To...Browser-Testing-Fr.. (40%)Code-Style-Standar.. (40%)Migration-Engineer.. (20%)

Agent Skills by TestDino

Showing 24 vetted skills indexed across 3 GitHub repositories.

testdino-hqtestdino-hq
347

playwright-core

Generate Playwright test guidance for locators, assertions, and waiting patterns.

Official
Advanced
testdino-hqtestdino-hq
347

playwright-cli

Automate browser interactions via Playwright CLI commands.

Official
Advanced
testdino-hqtestdino-hq
347

playwright-pom

Implement Page Object Model patterns for Playwright tests.

Official
Intermediate
testdino-hqtestdino-hq
347

playwright-ci

Configure CI/CD pipelines for Playwright tests with sharding and artifact merging.

Official
Advanced
testdino-hqtestdino-hq
347

playwright-migration

Convert Cypress or Selenium/WebDriver tests into Playwright test suites.

Official
Intermediate
testdino-hqtestdino-hq
9

google-styleguides-skills

Provide Google's official style guides for 17 programming languages and formats.

Official
Advanced
testdino-hqtestdino-hq
9

html-css

Enforce Google's official HTML and CSS style guide for web development.

Official
Basic
testdino-hqtestdino-hq
9

vim-script

Enforce Google's Vim script coding standards for plugin development.

Official
Intermediate
testdino-hqtestdino-hq
9

angularjs

Review AngularJS 1.x code against Google's official style guide.

Official
Basic
testdino-hqtestdino-hq
9

go

The official Google style guide for writing Go code.

Official
Intermediate
testdino-hqtestdino-hq
9

python

...

Official
Intermediate
testdino-hqtestdino-hq
9

shell

Generate Bash script templates following Google's Shell style guide.

Official
Intermediate
testdino-hqtestdino-hq
9

markdown

Format documentation according to Google's official Markdown style guide.

Official
Basic
testdino-hqtestdino-hq
9

typescript

Enforce Google's official TypeScript style guide for consistent code.

Official
Intermediate
testdino-hqtestdino-hq
9

r

Enforce Google's official R style guide for naming, functions, and data manipulation.

Official
Intermediate
testdino-hqtestdino-hq
9

java

Apply Google's official Java style guide to code snippets.

Official
Basic
testdino-hqtestdino-hq
9

json

Enforce Google's JSON style guide for formatting and naming conventions.

Official
Basic
testdino-hqtestdino-hq
9

cpp

Provide guidance on Google's official C++ style guide for coding standards.

Official
Basic
testdino-hqtestdino-hq
9

swift

Enforce Google's Swift style guide for naming, optionals, and formatting.

Official
Basic
testdino-hqtestdino-hq
9

csharp

...

Official
Intermediate
testdino-hqtestdino-hq
9

javascript

Apply Google's JavaScript style guide to ES6+ code.

Official
Basic
testdino-hqtestdino-hq
9

common-lisp

Enforce Google's Common Lisp style guide for naming, formatting, and macros.

Official
Basic
testdino-hqtestdino-hq
9

objective-c

...

Official
Intermediate
testdino-hqtestdino-hq
8

docs

Guide AI agents through TestDino MCP tools for test data access and analysis.

Official
Advanced

Frequently Asked Questions About TestDino

FAQPage Schema
What specific testing tasks does TestDino enable?

TestDino enables the implementation of Page Object Model patterns, generation of browser locator assertions, and configuration of sharded test execution. It facilitates the conversion of legacy test suites into modern browser-based frameworks while ensuring consistent code formatting across diverse programming languages.

Which personas benefit from these testing and style standards?

Quality assurance engineers, software developers, and DevOps practitioners benefit from these standards. The platform is designed for teams requiring rigorous adherence to established coding conventions and those seeking to modernize their browser-based testing infrastructure through standardized patterns and reliable migration paths.

What are the prerequisites for implementing these testing standards?

Implementation requires an existing codebase and a Node.js environment to support Playwright dependencies. Users must have access to their repository configuration to integrate the provided style guides and testing patterns into their existing build and verification processes.