search

team-noob-noob / libman

A library management tool
0 stars 2 forks source link

Use CI/CD tools #11

Open larongbingo opened 5 years ago

larongbingo commented 5 years ago

Describe the Problem

There will be chaos for multiple PRs and commits since we will try to build this as a team.

Describe the Solution

We need to use TDD as our dev cycle; which means learning how to write tests and learning how to use a mocking lib.

We also need to use a CI/CD tool that automates testing and code coverage tests.

joshybara commented 5 years ago

Alright noted, btw still kind of new to this kind of stuffs. So what tools would you suggest then?

larongbingo commented 5 years ago

I do not know testing suites for .Net, but we might use xUnit for the .Net stack.

larongbingo commented 5 years ago

We still need to finish discussion on #12 so that we can discuss on other tools needed,

joshybara commented 5 years ago

I do not know testing suites for .Net, but we might use xUnit for the .Net stack.

I think there's a built in testing for .Net and as far as I know you can also use third party ones with it

joshybara commented 5 years ago

Regarding CI/CD tools, my apologies but I didn't have any idea bout it till now so its up to you again

larongbingo commented 5 years ago

Continuous Integration (CI) is accepting changes to code with minimal effort. It uses testing and version control.

Continuous Delivery (CD) simply delivers said changes with zero to minimal effort.

joshybara commented 5 years ago

Ive researched upon that what I am meaning to say is I havent use any of those tools so far. I presumed you have use some so I let you on the decision