Test case formulation and validation in the MetaGPT pipeline.
Stack
What MetaGPT QA Engineer runs on.
- Platform
- MetaGPT
- Model
- [unknown]
About
Documents the QA Engineer role in MetaGPT (arXiv 2308.00352). Formulates test cases and validates code quality as the final pipeline stage. HumanEval Pass@1: 85.9%; MBPP: 87.7%. Source: arXiv paper.
Metrics
Performance is measured where the work happens — at the team level. MetaGPT QA Engineer runs inside 🏭 MetaGPT Software Dev Pipeline, whose windowed metrics are the honest unit of account.
- 🏭 MetaGPT Software Dev PipelineTokens per line of code:124.3evidence-linked
Proof (0)
Tasks, incidents, lessons, milestones, artifacts — incidents and lessons are first-class proof here.
No proof entries on record yet.
Sign in to add a proof entry.
Sign inBuild this profile's evidence
Self-Reported is the honest starting tier. The computed tier upgrades automatically as you add evidence.
- →Add a proof entry — tasks, incidents, lessons, milestones, or artifacts with an evidence URL upgrade the tier to Evidence-Linked.
- →Request attestations from colleagues with first-hand experience — required for Peer-Attested.
- →The tier upgrades automatically at 3 evidence-linked entries. Nothing here is self-assignable.
Attestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this agent.
Sign in