what type of review process u r following in u'r company?
- 4 Answers
- 11811 Views
- IBM, TCS, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / suneel reddy
Generally the Reviews are
Requirements REview
Design reviw
Code review
all these comes in verification strategy
| Is This Answer Correct ? | 5 Yes | 0 No |
Quality Management
Evince webwap tech's QA methodology builds upon widely
acknowledged industry standards of QA and is made up from
the following processes, known as the QA life-cycle:
Design review:
A thorough review of the processes and design of the
product/ application. Subject matter specialists and
designers perform this exercise. Architectural, Development
and Implementation issues are discussed and frozen at this
point in time. Our QA architects get involved at this stage
to determine the potential influence of architecture and
design on the QA process, platform and tools selection.
Unit Testing, Code Walkthrough
The most 'micro' scale of testing to test particular code
modules. Typically done by programmers and not by QA
engineers, as it requires detailed knowledge of the
internal program code. Not always easily done unless the
application has a well-designed architecture with tight
code; may require developing test driver modules or test
harnesses. Code walkthrough entails looking at a programmer
code. The idea of code walkthrough also ensures that a
programmer has used good coding practices and established
coding standards.
If THe answer is wrong let me know please.
| Is This Answer Correct ? | 2 Yes | 2 No |
I think there are three types of review process followed in
a company
1. SRS based review
2. BRS based review
3. TRM based review
| Is This Answer Correct ? | 1 Yes | 5 No |
As you are working with cmmi level 5 company ,can you tell me what processes you r following as QA engineer?
What is meant my Firewall testing? how the testing is performed on it?
How many testcases can you write per a day, an average figure?
consider therez 1 land and it has mango trees in it, what are the tets cases or how will we count no of mangoes on all trees
What actually you(Testing) people do when a new project starts. i.e can you give clear idea how testing is integrated with Project development &Release
We can check many things in one test case, then Is it necessary to write separate test case for checking each functionality? Example : For Login Window --> Test Case is---> 1) Enter valid user id & password --> For this expected result --> 1) User should login. My question --> while executing above valid test case, we can expect more than one result such as "Visibility of password should be as ****" So Should I have to write separate test case for "Visibility of Password" OR Not? Please guide me properly.
How do you conclude which section is most risky in your application?
Which are the standards for software test plans?
What is the difference between internal reviews and peer reviews?
Can anyone give me the usecase template???
from user point of view wht is the test case for notepad
Is an "A fast database retrieval rate" a testable requirement?
Automation Testing 
