QA Forums
Welcome on the QA Forums.

To take full advantage of everything offered by our software testing & Quality forums, please log in if you are already a member or join our community if you're not yet.... Smile


Join the forum, it's quick and easy

QA Forums
Welcome on the QA Forums.

To take full advantage of everything offered by our software testing & Quality forums, please log in if you are already a member or join our community if you're not yet.... Smile
QA Forums
Would you like to react to this message? Create an account in a few clicks or log in to continue.
Search
 
 

Display results as :
 


Rechercher Advanced Search

Navigation
 Portal
 Index
 Memberlist
 Profile
 FAQ
 Search
Who is online?
In total there is 1 user online :: 0 Registered, 0 Hidden and 1 Guest

None

[ View the whole list ]


Most users ever online was 36 on Wed Jan 10, 2018 12:25 am
March 2024
MonTueWedThuFriSatSun
    123
45678910
11121314151617
18192021222324
25262728293031

Calendar Calendar


Please answer the Following Questions as soon as possible.

2 posters

Go down

Please answer the Following Questions as soon as possible. Empty Please answer the Following Questions as soon as possible.

Post  sanazafar147 Sun Dec 23, 2012 10:25 pm

We are defining processes for company andwe need to establish a fluent
process for QA as well. we need to define QA involvement
from start to end in a life time of a project. These include answering few
questions:


  • What are industry standards?
  • What is the role of QA at every stage of a
    project (from requirement gathering to delivery/deployment)?
  • What is the input required from QA at every
    stage?
  • What is the out required by QA for testing at
    intermediate stages till the end?
  • What are those intermediate stages (depending
    upon the nature of a project)?
  • What documents should be developed by the team
    (software engineers/ managers) to be used by QA?
  • Format of those documents?
  • Reporting format?
  • Method to transfer subjected project from developers to QA for testing and
    vise versa?
  • Final approval method from QA?

These are just few points to start with for the upcoming projects.


As for the immediate action point when our projects are in the
middle or close to completion, please define what could be a smooth process of
handing over a project to QA (along with required docs), expected response with
expected time, developers first response to an error report and how we can
reduce cross communication or back n forth movement of project.

sanazafar147

Posts : 1
Reward Points : 3
Join date : 2012-12-23

Back to top Go down

Please answer the Following Questions as soon as possible. Empty Re: Please answer the Following Questions as soon as possible.

Post  shrutiC Fri May 17, 2013 12:05 am

Most of your questions will be answered by V model(Verification and Validation mode).
It gives you testing activities planned in parallel with a corresponding phase of development activities.

Documents that should be provided to QA include - Requirements documents , use case documents , design documents, release notes by development team stating known issues in release

Reg Method to transfer subjected project from developers to QA for testing and
vise versa.
Development team provides release emails to QA confirming the release in QA environment.
QA team provides signoff indicating end of testing.

Hope this helps Smile



Thanks,
Shruti Chaudhary
Infocepts Technlogies Pvt Ltd

shrutiC

Posts : 1
Reward Points : 1
Join date : 2013-05-16

Back to top Go down

Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum