Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thoroughly Document Developer Process for Testing Coded Additions to Splashkit #127

Open
njsch opened this issue Sep 14, 2020 · 1 comment · May be fixed by #137
Open

Thoroughly Document Developer Process for Testing Coded Additions to Splashkit #127

njsch opened this issue Sep 14, 2020 · 1 comment · May be fixed by #137

Comments

@njsch
Copy link
Contributor

njsch commented Sep 14, 2020

So far this does not appear to have been done in any great detail - I am still learning the ropes myself. It really should be documented somewhere as to how exactly to create and use test code. It's not actually as simple as writing a new library for modular inclusion: you have to also add_test to test_main.cpp and reflect this accordingly within the source file you have made changes to. Because this does not appear to be clarified, you have to manually locate the relevant files and then read the code to figure it out. This is not difficult but would take up less time with documentation.

@macite
Copy link
Member

macite commented Sep 15, 2020

Yes it would be great to get this documented. If anyone has time I'm happy to review and help contribute. Time is the big issue for me at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants