Do Agile projects use abbreviated defect reporting? [closed]
Closed 9 years ago.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
How do you identify bugfix commits on QA environment with Git repository?
I got used to the following approach on bugfixing phase of the project development. The developer should add SVN commit number as a comment to the JIRA issue when resolving it. Latest artifact from CI-server shows build number which include major version, branch name and commit number. This approach helps QA easily to identify whether the bugfix was included in the latest build or not. Even when same issue was reopened and fixed again.
What is proper order of pull requests and testing?
We want to setup proper development workflow.
We have two main branches: master(release branch) and develop(working branch).
We want to use pull requests properly.
We see two ways how to do this:
What is proper order of pull requests and testing?
We want to setup proper development workflow.
We have two main branches: master(release branch) and develop(working branch).
We want to use pull requests properly.
We see two ways how to do this:
What is proper order of pull requests and testing?
We want to setup proper development workflow.
We have two main branches: master(release branch) and develop(working branch).
We want to use pull requests properly.
We see two ways how to do this:
Whose responsibility is it to create the interface and/or acceptance testing? Developer or QA?
I am a backend developer and always create tests for my applications.
Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?
Whose responsibility is it to create the interface and/or acceptance testing? Developer or QA?
I am a backend developer and always create tests for my applications.
Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?