<feed xmlns='http://www.w3.org/2005/Atom'>
<title>yuzu-mainline/src/yuzu_tester/config.h, branch master</title>
<subtitle>A backup of the Yuzu mainline repo. Only includes the master branch, nothing else.
</subtitle>
<id>https://git.benis.co.uk/yuzu-mainline/atom?h=master</id>
<link rel='self' href='https://git.benis.co.uk/yuzu-mainline/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/'/>
<updated>2021-01-15T06:14:44+00:00</updated>
<entry>
<title>cmake: Remove yuzu_tester</title>
<updated>2021-01-15T06:14:44+00:00</updated>
<author>
<name>ReinUsesLisp</name>
<email>reinuseslisp@airmail.cc</email>
</author>
<published>2021-01-15T06:04:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=af540b00573e8c6b935289873ba624ecf81002ce'/>
<id>urn:sha1:af540b00573e8c6b935289873ba624ecf81002ce</id>
<content type='text'>
We never ended up using yuzu_tester.
Removing it saves code duplication with yuzu_cmd, and distribution size on
prebuilt packages.

For unit testing, we can use catch2 from guest code and dump the results
to a file. Then execute yuzu from a script on ci if we want this to be
automated.
</content>
</entry>
<entry>
<title>yuzu_tester: Use config, icon, and main from yuzu-cmd</title>
<updated>2019-06-10T04:03:11+00:00</updated>
<author>
<name>Zach Hilman</name>
<email>zachhilman@gmail.com</email>
</author>
<published>2019-03-26T00:30:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=819006d0d3232d66d303daabe701ca031e4caeae'/>
<id>urn:sha1:819006d0d3232d66d303daabe701ca031e4caeae</id>
<content type='text'>
</content>
</entry>
</feed>
