
As a QA Automation Engineer, Git is something I rely on every day. It helps me manage automation test scripts, review changes, and work on multiple features or bug fixes without impacting the main codebase. By creating separate branches for different tasks and merging them only after everything is tested, I can keep the workflow clear and organized.
I also appreciate how easy it is to track what has changed, revert mistakes when necessary, and collaborate with developers and other testers through pull requests. Because our automation framework is version-controlled, everyone stays aligned on the latest code, which reduces conflicts and makes releases run much more smoothly. Review collected by and hosted on G2.com.
Git works really well once you get familiar with it, but there’s definitely a bit of a learning curve—especially when it comes to branching, rebasing, and resolving merge conflicts. When multiple people are modifying the same files, sorting out conflicts can sometimes take a while. Aside from that, it’s been a very reliable tool for me, and I haven’t run into any major issues. Review collected by and hosted on G2.com.