-
Plan Test Cycles
How do you plan your test cycles in your current position?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 4th, 2009
A test cycle includes both a testing effort and a development effort to fix defects and deliver a new build to the test team. Elements of a test cycle that consume time are:
1) Software development effort to resolve defects and deliver a new build to test
2) Re-test bug fixes
3) Regression tests
4) Functional tests
In order to plan test cycles in a software development project, I would need to answer the following questions:
1) How much time do we have to fully test the software from the time this software is first introduced to test through the time the software is considered of good enough quality to release?
2) How stringent is the company's exit criteria? The more relaxed the exit criteria, the fewer test cycles will be required to satisfy it.
3) What are the number of test cases? The larger the number, the more time will be required to execute them during each test run.
4) What is the average duration required to execute test cases? The greater the number of steps and the greater their complexity, the longer it will take to execute test cases on an average.
5) How many testers will execute test cases? The fewer the number of testers involved, the longer it will take to complete each test cycle.
6) How many defects do you expect to find during each test cycle. The greater the number of defects, the more time will be required to verify them during test cycles.
7) How much time will be required for the development team to resolve defects between test cycles? Consider these factors: a) complexity of software, b) expertise of development staff, and c) the quality of communication between test and the
development staff.
8) How firm is the target release date? Will influential stakeholders allow this date to slip if significant issues arise?
9) What is the liklihood that major revisions of the software will occur during the testing phase of the project?
After receiving answers to these questions, I would plan a software project's test cycles.
Example:
1) Testing begins Feb 1, 2010 and ends Mar 31, 2010. We've got two months to fully test this application.
2) The software must have no more than 25 open defects and none of them can be Priority1 or Priority2.
3) There are 1000 test cases
4) The average tester can execute 50 test cases per day.
5) We have 5 testers.
6) Our company has been creating similar applications for some time and we do not expect an inordinate number of defects.
7) The development team can resolve issues and deliver a new build to testers in 3 days.
8) Marketing has already released a press release announcing the release date of the application, so this deadline is firm.
9) The company has done its up-front planning and we are confident the requirements are accurate, thorough, and will not require revision.
Calculations:
a. We have 43 business days to test this application
b. 50 * 5 = 250 test cases executed per day
c. 1000 / 250 = 4 days to execute all test cases in each test pass
d. Add a day for re-tests, regression tests and unexpected issues that may arise
e. 3 day turnaround for dev staff to fix defects and deliver a new build to test
f. Each test pass (all testing + bug fixes) will require 8 days
g. 43 / 8 = 5.375 test passes
This test project can have as many as 5 test cycles if necessary. If the product meets the exit criteria in fewer cycles, all the better.kurtz182
- Dec 4th, 2009
A test cycle includes both a testing effort and a development effort to fix defects and deliver a new build to the test team. Elements of a test cycle that consume time are:1) Sof...
sri1915
- Jul 16th, 2009
This is fully dependent on your project and business and user requirement.First analyse the requirement.
Develop the test plan.Start writing the test cases.Test Execution.Result analysis.Defect
Management.Summary. -
Tag a Release
What does it mean to tag a release? Why is it important to do this before testing?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 15th, 2009
One feature common to all version control systems is the ability to label or tag a release. Effectively, this provides a virtual “snapshot” of the state of all files at the time a release is built. In some systems like Clearcase, a label is attached to files, while in others, like Subversion, a label (or tag) is presented as a separate ‘directory’ in the repository. In either case, both allow you to turn the clock back to the moment of a release and rebuild things as they were at that time.
kurtz182
- Dec 15th, 2009
One feature common to all version control systems is the ability to label or tag a release. Effectively, this provides a virtual “snapshot” of the state of all files at the time a release ...
leo4rakesh
- Apr 15th, 2009
As far as I know, this means that a minor release must assure full compatibility with previous minor releases and you can guess why it is important by seeing the answer. As before any minor release it...
-
Improve QA Process
How will you begin to improve the QA process?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Dec 17th, 2009
Of course, the answer to this question depends on time, budget, and resources. Generally, this is how I would begin: I would evaluate QA processes based on past experience and the feedback that I've received from others (ex: Post Mortem - lessons learned). Then I would select projects that are feasible and will return the greatest value for our effort and focus my attention on them.
mailme.qualityfirst
- May 6th, 2010
Firstly we need to know is it QA process at ODC level, project level or org levelAt any level the present practise/process to be analysed and effective practices retained and overheads removed. If found any gaps inthe form of repeted defects try to define a set of procedure/process
kurtz182
- Dec 17th, 2009
Of course, the answer to this question depends on time, budget, and resources. Generally, this is how I would begin: I would evaluate QA processes based on past experience and the feedback that ...
-
Roles of Quality Assurance Manager and Project Manager
How do you differentiate the roles of Quality Assurance Manager and Project Manager?
Read Best Answer
Editorial / Best Answer
kurtz182- Member Since Nov-2009 | Nov 26th, 2009
I will answer this question as these roles apply to software.
Project managers are responsible for the overall success of software projects from conception to deployment. The tasks of a project manager include:
1) Creates and executes project plans and revises them as appropriate to meet changing requirements.
2) Manages daily operations of a project.
3) Ensures project documents are complete, current, and stored appropriately.
4) Reviews deliverables before passing them to client.
5) Enforces project standards.
6) Mitigates risks.Quality Assurance managers are responsible for the quality of software throughout the software development process. The tasks of a Quality Assurance manager include:
1) Establishes the environments and tools required to prevent and detect software defects.
2) Establishes quality standards and procedures to be employed throughout software development projects.
3) Creates and grows QA and Test teams through hiring and training.
4) Removes obstacles that impede quality assurance and test progress.
5) Delivers reports to stakeholders who need to make informed decisions about software quality.
6) Monitors and assesses QA and Test team performance.Jagdish.Narayan
- Aug 15th, 2010
Project Manager: PM is resposible for overall successfull delivery of the project.QA manager: Is just ensure that wherever product has been developed under supervision of him/her has quality oriented.
kurtz182
- Nov 26th, 2009
I will answer this question as these roles apply to software. Project managers are responsible for the overall success of software projects from conception to deployment. The tasks o...
-
Why do you have to build a QA environment to conduct a performance test? What issues have you faced building a QA environment?
Syama
- Mar 6th, 2007
The reason for building a QA environment is to simulate the conditions under which the product is going to be ...
Nik_Agarwal
- Oct 5th, 2006
We need to buid the QA environment for performance testing because to check the performance we need to monitor response from the Web Server and Database Server, through these servers we get the infor...
-
Hi, What are the challenges QA Analyst faces? (Urgent) I have this question in my interview, can anybody help plz. Thanks
poornima_lpr
- Aug 11th, 2008
QA Analyst has to take care of the entire testing process to prevent the bugs its called verification.
BestResult
- Aug 8th, 2008
There could be many challenges in QA.Deadlines.Work under Pressure conditionsUnderstanding the new requirements and coming up with best testcases.For me the challenge was when a software product Quali...
-
How do you perform system readiness and operational readiness tests
Ritik1008
- Sep 30th, 2008
System readyness testcan be done by checking Required system configaration as per mentioned in SRS or configration document.To check configration is systematically placed(as per the spec) is called S...
-
How can we perform testing without expected results?
arvind.krs
- Mar 8th, 2009
In brief, "Adhock" testing or "free form" testing which are done without having any test scripts are known as testing without expected results. But keep in mind that in these c...
vk1978
- Mar 7th, 2009
Suppose, if an application is already developed and with some older Technologies (ex MS Access or VB) and wanted to upgrade whole application with new technologies like .NET or Java, in this scenario ...
-
If we have 50 functional requirements in S/WRS document and we prepared test cases for that document. How can u find the mistake or loss the functionality in SRS document? Is it possible to review in Traceability Matrix?
vk1978
- Apr 17th, 2009
With the question, what i understood is you have 50 requirements but what if there are mistake available or Not availability of functionality in SRS document... If all the requirements are not covered...
Dhananjay
- Aug 13th, 2007
Generally Traceability matrix and detailed test case docs are prepared in separate spread sheet. Test cases identified in the RTM are maintained in the different spread sheet which will be comprised o...
-
What is Requirements Traceability ? What is the purpose of it ? Explain types of traceability matrices ?
vk1978
- Apr 17th, 2009
Traceability Matrix - In simple words mapping requirements with Test cases As documents are interdependent the data present in the child document (Test case document must be based on Parent docum...
G.D.S.Prasad
- Dec 20th, 2006
Hi,Traceability Matrix: A document showing the relationship between Test Requirements and Test Cases.It demonstrates the relationship between design inputs and design outputsIt ensures that design is ...
-
Difference between Configuration Management and Version Control.
SUSHALL
- May 28th, 2009
Hi Sreekanth,I could not exactly get what you are trying to say. May be am not used to most of the technical words you have used. I request you to clarify me in a simple way for my questions.1. We say...
Sreekanth Reddy Lingala
- Jun 20th, 2006
Version Control is part of Configuration Management. Read the following, you will understand.Configuration Management is the approach used in managing the individual components (software & hardwar...
-
QA Process
1. In QA team, What does the term Process refer to?2. What are the different type of process?
kurtz182
- Dec 17th, 2009
Process refers to a set of interdependent procedures that serve to produce a desired result. Its meaning is no different in QA than anywhere else. QA processes include:1) Te...
sameerponkshe
- Oct 8th, 2009
Process means Quality proceses followed during the project executions, the high level processes are 1. Project Management Processes2. Change Management Processes3. Defect Management Processes4. Requirement Management Processes
-
QA Professional Task
How does QA verify that existing product functionality is still working while verifying new product features and functionality?
mailme.qualityfirst
- May 6th, 2010
It is again functionality testing. But when new features are added, we call it regression testing. First test the newly added features, if you find bugs then take a decision to carry on testing based on criticality and later test the old featuresHope its right!
-
What is the difference between System Testing,Integration Testing & System Integration Testing?
manii17k
- Oct 22nd, 2010
Once the application is installed into a environment as a whole is called as system testing in this stage the black box test engineer will perform many types of testing they are 1 . System integrati...
Rose1
- Oct 21st, 2010
System Testing:In system testing we test the system works well in the real environment with the real data. Since the servers and data are different it may not work as expected.Integration testing:In i...
-
What is an exit and entry criteria in a Test Plan ?Please explain
michaly
- Sep 20th, 2011
In exit Criteria: I like to add to Santhoshi Kotha thorough answer: Risk. everything based on the Risk!
Santhoshi Kotha
- Sep 16th, 2011
The Entry andExit criteria are clearly mentioned in the Testplan: The Entry criteria is: 1. All the integration exit criteria has been sucessfully met. 2. All the installation documents have been comp...
-
UAT Testing
I am asked as to how many test scernarios will be typically created in a mid size project. I think this question does not make any scense as the scenrios is always based on the requirement and scope of the project. but I guess my answer is wrong and I did not get the project. Can anyone tell me what is the correct answer to this question..Thx
mithr17
- Oct 14th, 2011
Wow that's a really stupid question which you answered it correctly. As Gypsyqueen said there may be other reasons not just this one. The next time anyone asks you this question, you should put them ...
Gypsyqueen
- Sep 26th, 2011
Your answer sounds correct to me. Maybe there are other reasons you did not get the project.
-
QA Testing : What are the key elements for creating test plan?
Read Best Answer
Editorial / Best Answer
Answered by: BISWAJIT PANI
- Jun 15th, 2006
1) Objectives
2) scope
3) Approach
4) Testing Methodology
5) Assumption
6) Risk
7) Contigency paln
8) Delivarable
9) Defect Reporting
10) Efforts and Estimation
11) Entry and Exit Criteria
12) Roles and Responsibilities
13) Schedules
14)Testing environment
etc.......
Regards,
Biswajit pani ( 09986183456)
Sridhar Dommati
- Nov 7th, 2011
the question is "what are the key elements for creating Test Plan"? but all the people telling the contents of a Test Plan according to my view... "Test plan is a master document..which contains s...
santhishini
- Sep 21st, 2011
Quality assurance for preventing defects and qc for detecting defects.............
qa is done by developer and qc done by test engineer -
-
Explain about Metrics and types of metrics like schedule variance , effort variance?
parameshwar.V
- Dec 17th, 2013
Effort Variance should be (Actual Effort - planned Effort)/ Planned Effort.
EV should calculate w.r.t Person Days.
Schedule variance should be (Actual End Date - Planned End Date)/Planned End Date.
SV should calculate w.r.t Person Hours.
av45738
- Nov 20th, 2009
Effort Variance= (Actual effort-estimated effort)/Estimated effort*100Schedule Variance=(Actual elapsed time- estimated elapsed time)/estimated elapsed time*100
-
Agile and scrum
What is the difference between agile and scrum
QA Testing Interview Questions
Read Best Answer
Ans