[Community Request] Increase coverage in our repo

[sync-by-unito[bot]]

Unit test coverage provides a way to know how much of your code is covered via tests.

Our overall coverage is around 45% but it should be higher.

For those looking to contribute, this is a good starting point!

I suggest getting PRs small (one file at a time).

┆Issue is synchronized with this Jira Task by Unito

[sync-by-unito[bot]]

➤ Kevin Hannon commented:

https://app.codecov.io/github/armadaproject/armada/tree/master

[sync-by-unito[bot]]

➤ Dinuka-Thathsara commented:

Hi.Sir! I'll work on this.

[sync-by-unito[bot]]

➤ Kevin Hannon commented:

Please just comment on a file you’d like to improve and then work on it

[sync-by-unito[bot]]

➤ Dinuka-Thathsara commented:

sure

[sync-by-unito[bot]]

➤ Maureen Ononiwu commented:

Okay I would look through the files kannon92

[sync-by-unito[bot]]

➤ Maureen Ononiwu commented:

Currently working on writing test for internal/scheduler/adapters/adapter.go file

[sync-by-unito[bot]]

➤ Akash Kumar Saw commented:

/assign

[sync-by-unito[bot]]

➤ Maureen Ononiwu commented:

Heyy @akash-kumar-saw, a lot of us are working on this issue, you would just have to pick a file and write a test for it.

[sync-by-unito[bot]]

➤ Maureen Ononiwu commented:

I would be wriring a test the internal/lookout/server/lookout.go file