search

GatorEducator / cellveyor

GNU General Public License v3.0
3 stars 7 forks source link

Write Tests for All Existing Features #12

Open hayleepierce opened 11 months ago

hayleepierce commented 11 months ago

Determine what parts of the code need to be tested and write the test cases.

gkapfham commented 10 months ago

Thanks for raising this issue @hayleepierce!

It might be worth it for members of the team to walk through the source code in the existing version of the program and find the parts of it that are (i) the easiest to test and (ii) in the greatest need of testing.

It is worth bearing in mind that there are parts of this system that are likely to prove very difficult to test because of the fact that they are going to interact with a remote Google Sheets and/or Google Drive API. We may have to create "mocks" or "stubs" to help with this task.

Although he is not currently in this repository or this organization, Alish has some experience with writing test cases for a part of a program that use a remote, third-party API.