Skip to main content
Tweeted twitter.com/StackSQA/status/1240926189948153856
added 4 characters in body
Source Link
JAINAM
  • 1.8k
  • 3
  • 18
  • 39

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place.

My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for a retest to QA
  • QA will certify an app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project.

I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? We don't have a business analyst/writer. Is there any thinganything I could improve on the process? Feel free to comment on my existing process.

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place.

My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for retest to QA
  • QA will certify app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project.

I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? We don't have a business analyst/writer. Is there any thing I could improve on the process? Feel free to comment on my existing process.

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place.

My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for a retest to QA
  • QA will certify an app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project.

I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? We don't have a business analyst/writer. Is there anything I could improve on the process? Feel free to comment on my existing process.

deleted 4 characters in body
Source Link

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place. 

My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for retest to QA
  • QA will certify app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project. I

I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? weWe don't have a business analyst/writer. Is there any thing I could improve on the process? thanks and feel Feel free to comment on my existing process.

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place. My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for retest to QA
  • QA will certify app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project. I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? we don't have a business analyst/writer. Is there any thing I could improve on the process? thanks and feel free to comment on my existing process.

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place. 

My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for retest to QA
  • QA will certify app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project.

I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? We don't have a business analyst/writer. Is there any thing I could improve on the process? Feel free to comment on my existing process.

Source Link
Marj
  • 1.4k
  • 2
  • 12
  • 27

How to organize a QA Process/Department?

I am in a 10 man team, and I am the only QA in the team. I am new to the team and I have already put a QA process in place. My process is this:

  1. Development (will wait till the development phase is done)
  2. QA will do the testing
  • QA will create test cases off of the developer's story and what I see on the existing app(yes, the team does not have any documentation at all, including requirements)
  • QA will then execute test cases
  • QA will assign bugs to developers; developers reassign bugs for retest to QA
  • QA will certify app
  1. QA will report the summary to the Project manager and developer, giving the 'go' sign for production deployment

Then repeat the process to the next project. I know, for a fact, that I still lack something in the process. Since documentation is not there, which is the business documents/process documents, is it practical for me to create these documents first before creating all these test cases? we don't have a business analyst/writer. Is there any thing I could improve on the process? thanks and feel free to comment on my existing process.