3 ms·
I don't understand the issue, in mobile development you can also test changes as soon as the build is done and see if there are bugs. You can also publish (at l
by thecupisblue 11y ago
I don't understand the issue, in mobile development you can also test changes as soon as the build is done and see if there are bugs. You can also publish (at least for Android) directly from CI to play store Alpha/Beta/Release and have that go straight to QA. You can build a branch on PR and have a link sent to your QA team via slack.
> One is that suppose we merged some feature into development and later figured out that there are lot of bugs in it. Now it can’t be pushed further, whole development cycle is stuck because that code is already merged with development
Why is buggy code being merged in? Why isn't it reviewed,covered with tests and tested manually?
Also, you can checkout commit before merge, create a new branch and continue development without any issues.
- prats226 11y agoYeah I agree we are lacking in sufficient testing right now because since we are in early stage of app development, we are building features at fast pace. One solution is to merge changes using --no-ff flag and using revert to remove changes if there is major bug in that merge.