# WriteFreely Automated Testing

**URL:** <https://discuss.write.as/t/writefreely-automated-testing/1901>\
**Category:** Development\
**Created:** [October 9, 2020, 1:52pm UTC](https://discuss.write.as/t/writefreely-automated-testing/1901 "2020-10-09T13:52:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![colin-axner](https://discuss.write.as/user_avatar/discuss.write.as/colin-axner/32/919_2.png) [@colin-axner](https://discuss.write.as/u/colin-axner)\
**Post date:** [October 9, 2020, 1:52pm UTC](https://discuss.write.as/t/writefreely-automated-testing/1901/1 "2020-10-09T13:52:44Z")

</div>

I find writing tests to be an excellent way to familiarize myself with a new code base. I was thinking of attempting to add some unit tests for WriteFreely. I think this will help cut down technical debt related to hunting down bugs/manually testing changes.

Is there any preexisting discussion how to standardize this process? I am specifically referring to the go files in the codebase. From my experience it is useful to have a centralized testing structure that can initialize/setup a generic testing environment for testing more in-depth functions and integration tests as well.

Is there any files that I should start with? Maybe because they’d be easier to add unit tests for or because they frequently have bugs appear?