PS2 EE-Core Specific Unit Tests

Open
#159 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
testing-qa

Research direction

Start by locating the existing unit-test setup and the implementations of MMIFunctions, MMI0Functions, MMI1Functions, MMI2Functions, MMI3Functions, and PMFHLFunctions. Run the existing tests, then identify which instructions in those groups lack coverage. Done means every instruction has a basic test and relevant edge cases, such as saturation and flag setting, are covered.

Written by the indexing model from the issue text.

Description

enhancement recompiler

To validate correctness for each translated instruction, we need to construct unit tests for each instruction that the PS2 EE-Core can possibly execute. Each instruction should have at least one basic test, as well as cases for edge behavior, like saturation, flag setting, etc.

The PS2 EE Core Specific instructions that require testing:
MMIFunctions
MMI0Functions
MMI1Functions
MMI2Functions
MMI3Functions
PMFHLFunctions

Dominant language
C++
Stars
3.3k
Forks
149
Avg merge
8h 46m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ran-j/PS2Recomp

All issues in ran-j/PS2Recomp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.