Skip to content

Add richer testing skills as default for Codex #242

@huydao226

Description

@huydao226

Hi team,

I’ve been using Codex to build many small websites for stores and landing pages.

At the moment, the default testing skill seems to focus mainly on Playwright interaction. That is helpful, but in practice it still requires quite a lot of effort to prepare a strong master prompt and define the testing guidance before Codex can test effectively.
I’d like to request an investigation into improving the default testing skills in Codex, or adding a more complete testing skill set by default.

Some areas that would be valuable:

  • Better default guidance for exploratory testing, not only browser interaction
  • Support for common website checks such as UI/UX issues, broken flows, form validation, edge cases, and responsiveness
  • More structured bug reporting output
  • Smarter defaults so users do not need to spend too much time writing a master prompt
  • A more complete testing workflow that feels closer to real QA, not just scripted Playwright actions

This would be especially useful for users like me who use Codex to quickly build and validate many small websites. Right now, the current default is a good start, but it still feels too low-level and prompt-dependent.

Would anyone be able to investigate this and consider expanding the default testing skill experience?

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions