SJW <shannon.whi...@gmail.com> writes: > Getting QA Involved. > > Do you have a guide or process I could use to get QA involved?
I'm afraid there's nothing like that, that it's very dependent on the organisation you work in. In the past I've had some success with "leading the horse to water". Another approach is to "find a friend" in QA, someone who's interested in improving how they work with you. > I've been thinking about this ... If they could go to GitLab and > "deploy" a branch to staging for testing then that would work. Just that you're using Gitlab is a great thing. You should start using GitlabCI, if you aren't already. I suggest thinking a bit about options, things like - what if you set up GitlabCI to package up a build on a branch, can you make it trivial for QA to take that and put that in your staging environment? (Something like a script, mabye. I'm assuming QA is as computer savvy as you.) - what if you completely skip staging, instead you have GilabCI build a Docker image that QA can consume? Can QA do all they need to do with a locally running setup (you can provide a Compose[1] file to help that)? > Each time they test - go to GitLab -> select branch -> somehow deploy > to stating server This is a bit like the first option above. /M [1]: https://docs.docker.com/compose/ -- Magnus Therning OpenPGP: 0x927912051716CE39 email: mag...@therning.org twitter: magthe http://magnus.therning.org/ Only put off until tomorrow what you are willing to die having left undone. — Pablo Picasso -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/87wo3bg5au.fsf%40therning.org.
signature.asc
Description: PGP signature
