Organizing tests on Github, good practice?

Asked

Viewed 44 times

1

I’m currently doing a research for automate and organize the software testing.

Amid the researches found some tools, but I believe that a new tool would not be so productive because the developers would want to familiarize themselves with it.

However, for not wanting to have another working tool, I thought organize the system requirements in the Github and do all test reports there. Also organizing in tags, as an example, tested, approved, failed and similar.

This is considered a good practice for testing? Or really is necessary another tool?

  • What you want is to store the test results in Git, is that it? But you’re going to use a test tool, right? Unit testing, automated, acceptance, ...

  • @Exact! Git would store the results and feedback on the Ports

  • I don’t think it makes much sense to claim that "a new tool wouldn’t be so productive..."; understand that Git is a source code management tool. If you have PO’s that want to access the results of these tests, they should know Git for this, which doesn’t make much sense, do you agree? What’s your development platform? Language? In addition to Git, what else do you use? So I can give you an answer

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.