# Way to test errors in my code

**URL:** <https://forum.choiceofgames.com/t/way-to-test-errors-in-my-code/89401>\
**Category:** General\
**Created:** [November 7, 2020, 5:23am UTC](https://forum.choiceofgames.com/t/way-to-test-errors-in-my-code/89401 "2020-11-07T05:23:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Loudbeat](https://sea3.discourse-cdn.com/choiceofgames/user_avatar/forum.choiceofgames.com/loudbeat/32/115975_2.png) [@Loudbeat](https://forum.choiceofgames.com/u/Loudbeat)\
**Post date:** [November 7, 2020, 10:56am UTC](https://forum.choiceofgames.com/t/way-to-test-errors-in-my-code/89401/3 "2020-11-07T10:56:44Z")

</div>

Quicktest and randomtest should work afaik, in my experience they are the best tools to find bugs and track stats.  
Here is a modified version of the tool in which you can track stats without the need to print the whole text, which is really useful to me

> [@Generate Statistics About Your Stats](https://forum.choiceofgames.com/t/generate-statistics-about-your-stats/76175):
>
> To help me balance my stats in my work-in-progress, I modified randomtest to take snapshots of my stats and put them in a .csv file, which Excel and other spreadsheet programs can open. I put the changed code [on Github for anyone who wants to give it a try](https://github.com/sgranade/choicescript). You should be able to use it just like you would ChoiceScript from the main repository. To try this out, in your startup.txt file, put a special comment that sets up what variables to save: \*comment savestatsetup [stat1] [stat2] [stat3] Re…

---

_[View the full topic](https://forum.choiceofgames.com/t/way-to-test-errors-in-my-code/89401)._
