RPCS3/ps3autotests
1
0
Fork 0
mirror of https://github.com/RPCS3/ps3autotests.git synced 2024-11-08 11:52:58 +01:00
Code Issues Projects Releases Wiki Activity
Mirror of https://github.com/RPCS3/ps3autotests
15 Commits 1 Branch 0 Tags 8.3 MiB
Self 88.6%
C++ 10.1%
C 0.7%
Python 0.6%
763d903919
Go to file
Alexandro Sánchez Bach 763d903919 Tests added: rsx/rsx_fp_static 
The fragment shader draws something static on a fullscreen quad (two
triangles). The results from a real PS3 are saved in *.expected.png. The
source code of the fragment shader is saved in the *.cg files.
2014-03-30 17:22:42 +02:00
tests Tests added: rsx/rsx_fp_static 2014-03-30 17:22:42 +02:00
utils Script added: PS3 Logs -> .expected file 2014-03-05 01:10:42 +01:00
.gitignore Tests added: rsx/rsx_fp_static 2014-03-30 17:22:42 +02:00
LICENSE Initial commit 2014-03-01 04:24:48 -08:00
README.md Test added: cpu/hello_world 2014-03-03 02:58:27 +01:00

README.md

PS3 Autotests

A repository of PS3 programs performing several tests on the PS3 platform. Inspired by the PSP Autotests repository, and shares some goals with it and proposes some other ones:

  • Provide a platform for benchmarking PS3 emulators and comparing their performance with a real PS3.
  • Allow people to see how to use some obscure-newly-discovered APIs and features.
  • Allow PS3 emulators to avoid some regressions while performing refactorings and to have a reference while implementing APIs.

The main idea behind this is having several files per test unit:

  • file.expected: File with the expected TTY output, preferably from a real PS3.
  • file.elf: The program that will call printf / sys_tty_write SysCall in order to generate an output.
  • file.c: Include the source code or at least a brief description of the unit test (Optional).

Building the tests

TODO

Running tests on a real PS3

TODO

Running tests on a PS3 emulator

TODO