2 added 8 characters in body
source | link

Typical process (for us, anyway) is

  1. Developer codes the feature point or bug fix, as well as any automated tests
  2. Developer performs a local build
  3. Developer performs local unit testing
  4. Developer submits for code reviewDeveloper submits for code review
  5. Lead developer or peer developer reviews the codeLead developer and/or peer developer reviews the code
  6. Developer checks code and automated tests into code repo
  7. CI server detects code changes and pulls latest code
  8. CI server generates a build and executed automated tests again
  9. At regular intervals, builds are installed on a QA environment
  10. QA performs functional testingQA performs functional testing

Since the code review occurs before the code checkin, it would be unusual for QA to perform any testing concurrent with the code review, since they would have to testing an unofficial build. Generally speaking they are going to want to stick to testing actual builds.

Typical process (for us, anyway) is

  1. Developer codes the feature point or bug fix, as well as any automated tests
  2. Developer performs a local build
  3. Developer performs local unit testing
  4. Developer submits for code review
  5. Lead developer or peer developer reviews the code
  6. Developer checks code and automated tests into code repo
  7. CI server detects code changes and pulls latest code
  8. CI server generates a build and executed automated tests again
  9. At regular intervals, builds are installed on a QA environment
  10. QA performs functional testing

Typical process (for us, anyway) is

  1. Developer codes the feature point or bug fix, as well as any automated tests
  2. Developer performs a local build
  3. Developer performs local unit testing
  4. Developer submits for code review
  5. Lead developer and/or peer developer reviews the code
  6. Developer checks code and automated tests into code repo
  7. CI server detects code changes and pulls latest code
  8. CI server generates a build and executed automated tests again
  9. At regular intervals, builds are installed on a QA environment
  10. QA performs functional testing

Since the code review occurs before the code checkin, it would be unusual for QA to perform any testing concurrent with the code review, since they would have to testing an unofficial build. Generally speaking they are going to want to stick to testing actual builds.

1
source | link

Typical process (for us, anyway) is

  1. Developer codes the feature point or bug fix, as well as any automated tests
  2. Developer performs a local build
  3. Developer performs local unit testing
  4. Developer submits for code review
  5. Lead developer or peer developer reviews the code
  6. Developer checks code and automated tests into code repo
  7. CI server detects code changes and pulls latest code
  8. CI server generates a build and executed automated tests again
  9. At regular intervals, builds are installed on a QA environment
  10. QA performs functional testing