What Methodology is followed in your testing?
Answers were Sorted based on User's Feedback
Answer / munikumar
thank you js,
please explain about agile model
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / aryaa
All above answrers i will not comment anything.
But what i say i think it is the right answer for the
question,
there are three methodolgy prevailing, that are:-
1-Adhoc Metodology
2-Agile Methodology
3-Scrum Methodology
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / niturao
What is spiral testing could u explain it mamta? thanku
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / ann
Yes methods depends on what SDLC models your company is
using....
The black box, white box, and gray box are classification
or type of what we called FUNCTIONAL TEST...
SDLC PHASES are mentioned by Ramjay (but commonly it is
composed of six steps only)
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / dave
hi guys,
i think mamta has posted the right answer...if u have doubts
on testing methodologies, refer in the below link:
http://www.buzzle.com/articles/software-testing-methodologies.html
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / srinivas
generally blackbox teting methdology is folowed
in my testing
| Is This Answer Correct ? | 3 Yes | 5 No |
Answer / sharads
hi all,
I think Methodologies are as follows
Methodology depends upon the SDLC
1.Water fall
2 prototyping
3 spiral
4 V Module
Regards,
Sharad
| Is This Answer Correct ? | 0 Yes | 2 No |
Answer / me right
All of you are wrong the correct answer is Test Tst t
| Is This Answer Correct ? | 0 Yes | 4 No |
Answer / mamta
hi all,
I think Methodologies are of 3 types
Methodology depends upon the SDLC
1.Water fall
2 prototyping
3 spiral
most of the companies are using Spiral one because if any
NEW risk enter while working ,we can handle it.
Regards,
Mamta
| Is This Answer Correct ? | 1 Yes | 8 No |
i have completed software testing.Can anyone send sample and simple srs document for writing test cases.
An engineering college wants to automate their examination activities to speed up their work and maintain high-end accuracy of information. A brief overview of the proposed system is given below: The proposed examination system is consisting of 8 semesters spread across 9 branches (assume your own branch names) and spans over a period of 4 years. Each student belongs to a branch and must register for a minimum of 6 courses but not exceed 8 courses maximum. The scoring pattern for each course is given as below: Maximum marks for each course: 100 Pass: 35% Distinction: 70% and above First class: =>60% and <70% Second class: >50% and <60% Pass Class: >=35% and <50% The proposed system computes the result and announces the results every semester. The results must be accurate and all examination records will be maintained till the students leave the college. Develop a Test Strategy to test the proposed system. Your Test Strategy must include the following: • Test Plan • Testing Methodology to be followed • Test cases • Test effort estimation • Test Correction Mechanism Note: If you need more information on the requirement specification, you are permitted to assume along the same line but clearly specify the details.
Hello friends.. Can anybody here explain me or provides me notes of these topics in detail with interview questions... Topics are:- History of Software Engineering Waterfall Model Prototype Model Spiral Model Software Quality Testing Software Development Life Cycle Software Testing Life Cycle white box testing methodology black box grey box Definition of Quality,Quality Assurance,Quality Control Verification and Validation Static Testing Dynamic Testing only on my gmail mca.rachna21@gmail.com
What Methodology is followed in your testing?
Why I think QA is the positon for me
Test Documents Reporting answers
How do you document well a website (i.e an ONG website) pls help me with a sample. Need your help UR
what is the format of traceability matrix
what are the fields in Bug Report
how many levels of regression testing is avilable in our testing process?
How do we do testing if requirements are not documented properly?
After asking the defect life cycle, if you think it is not a valid defect, what you will do, whether you will store in any document for future reviews,if yes, what is that document, where you will save that document? or just reject it and close it?