My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 517: QA functionality
4 people starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Mar 2010


Sign in to add a comment
 
Reported by maca...@gmail.com, Mar 30, 2010
I am willing to start using gerrit in my project.
We are two android devs and a QA analyst.

I guess the best way to involve a QA right now is:
 * devA pushes a change
 * devB code reviews it and accept it
 * QA pulls from master and checks functionality

I don't know which is the correct workflow to follow if the QA founds 
something wrong but it would be cool if we can set up gerrit to make our 
pushes acceptable only if they pass the code review and the QA process.

Also it would be nice if gerrit can be configured to show a "Download the 
patched apk" so the QA doesn't need to compile the change himself.
Mar 31, 2010
#1 nas...@chromium.org
Why wouldn't your QA person use the 'Verified' field?
Mar 31, 2010
Project Member #2 lscar...@gmail.com
And if the Verified bit is not what you want you can go to the DB and create your
own... of change Verified's wording. Please see the documentation:
http://gerrit.googlecode.com/svn/documentation/2.1.2/access-control.html#category_makeoneup
Status: Invalid
Sign in to add a comment

Powered by Google Project Hosting