Shankar

• Jul 26th, 2015

Horizontal trace-ability matrix documents the inter-dependency between requirements. Once dependency identified it will be easy perform impact analysis.

jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Dec 30th, 2006

Vertical traceability of the requirements describes the interdependencies among the system requirements.Horizontal traceability addresses the relationship of the components across collections of workproducts

Answer Question  Select Best Answer

Read Best Answer

Editorial / Best Answer

srinivasulub1981  

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Member Since Dec-2005 | May 2nd, 2007

---

If the customer changing the reqs ...  : If the change came in between the testing time of previous requirement ( change) then i can stop testing and intimated to my TL... if the change came after completion testing of prev change then i can go for testing .. I think in this situation we can't do anything like reporting to PM or any except doing testing for new changes..  at present we doing like this only..  coz all the risk analysis, cost estimations are already done by PM and given it for testing..

Suppose you have....  :  In between we can review test cases ( by me or peer)..  try to prepare effective test cases , or can test application upto completion part if possible...

How you know.....   : 1. Daily we check the BTS for bug status
 
2. Actually we sent a mail with bugs to concerned developers to fixed, he revert back   with status of bugs, then we can go for re testing.

3.If using any test management tool, if automatic email configuration is configured then concerned tester should receive a conformance email that the bug is fixed...

narendra

• Oct 1st, 2015

As per Project is concerned, we are working for customers and their requirements to be met... so in this case I hope every tester must be flexible at any moment and accept the change at any time... an...

vasudha

• Apr 21st, 2015

The information at. The top of the file is XML namespace

Improve Answer

If a bug is not reproduceable then what testing team will do?

pravati

• Jan 9th, 2016

If a bug is not re-produceable then the tester again check the bug and give some more details like screenshot and detailed steps.

okesh

• Jul 29th, 2015

According to bug life cycle -- change the status as closed

Answer Question  Select Best Answer

IF we enter correct username and incorrect password while login to yahoo mail account, why the error message displayed in "Invalid ID or Password" though I have entered correct ID?

Abhishek

• Jan 22nd, 2016

The answer to your question is security reason. Imagine an unknown person(Intruder) is randomly trying to enter username/ password for a user. If the system mention the error message as "Password is ...

Nir

• Jan 7th, 2016

"Invalid Credentials, try again"

Answer Question  Select Best Answer

Actual functionality is - if user want to take the print then print check box should be checked otherwise print wont come if check box is not selected at the time of saving data.
BUG - Print of the saved data is coming even user did not select the print checkbox.
Developer correct the issue and release the bug. During regression testing bug found that print is not coming even if checkbox...

deepa

• Feb 15th, 2017

Bug should not be rejected, because originally it was correct and was fixed. If you reject this bug even when related issue wasnt actually a bug, then the authenticity of the original issue is lost

Answer Question  Select Best Answer

venkat reddy gopu

• Jun 19th, 2017

Application Under Test

Prerit

• Aug 11th, 2016

AUT stands for "Application Under Test". Once the development team is done with the coding part of Software Development Life Cycle(SDLC), then the build is progressed to Testing for validating and ver...

Answer Question  Select Best Answer

Definition of Defect Tracking tools and why is it necessary in software testing? Present what type of tools are available in market?

Prarthana Wahi Manchanda

• Jul 13th, 2017

Defect Tracking tool is a software which keeps track of all the reported bugs

Famous defect tacking tools are:
Microsoft test manager
TFS
ALM QC
Jira
Rally
Mantis
Bugzilla

bhaskar

• Jul 5th, 2016

Jira, Track +, Bugzilla etc

Answer Question  Select Best Answer

Prarthana Wahi Manchanda

• Jul 13th, 2017

Test summary report is a formal document that summarizes the results of all testing efforts for a particular testing cycle of a project / module or a sub module. Generally, test leads or test managers prepare this document at the end of testing cycle.

Components of a Test Summary Report

• Feb 11th, 2016

You may want to add these components as part of a Test Summary Report ;- Phase of Testing Type of Testing Test Plan Reference Test Environment Executive Summary (road blocks,deviati...

Answer Question  Select Best Answer

Pari

• Oct 5th, 2017

P1- Blocker issues, for eg, Unable to install the app; P1 bug is the priority 1 bug that means without solving or fixing this bug the application cannot continue

dhananjay

• Jun 29th, 2015

P1: Blocker (Show Stopper )
P2: Critcal
P3: Major
P4: Minor
P5 : Trivial

Answer Question  Select Best Answer

Piyush Patwa

• Nov 15th, 2017

I was asked a similar question during testing interview. The negative test case scenario issues are the most prominent bugs that you come across. Suppose you are testing a Phone and the LAN wire cable...

manoj kumar

• Feb 5th, 2017

Currently am going to work on ERP domain. Could you please represent me some issues regarding this domain?

Answer Question  Select Best Answer

Piyush Patwa

• Nov 15th, 2017

During the process of sufficing software requirement in the development. If the bugs are missed out in the initial phase . They impact the software significantly and when they are caught in the later phase of testing these bugs are called latent bugs. (As latency signify delay in a process)

vinodkumar

• Feb 15th, 2017

Latent Bugs : Which are bugs that didn't find early stages up to more than 2 builds are released then find that hidden bugs we call Latent Bugs.

Answer Question  Select Best Answer

Piyush Patwa

• Nov 15th, 2017

Bug: Flaw in system deviating from expected behavior.(Flaw In the whole system)
Defect: A flaw in a component or system that can cause the component or system to fail to perform its required function.(Flaw in a Componenet)

venkat reddy gopu

• Jun 19th, 2017

The Error Which is found by Tester is Called Defect.
Defect Accepted by Development Team is Called Bug.

Answer Question  Select Best Answer

Piyush Patwa

• Nov 15th, 2017

Introduction 1.1 Purpose of the Document 1.2 Scope of Software Test Plan 1.3 Acronyms and Definitions 2 Scope of Testing 2.1 Features Details 2.1.1 Features to be tested 2.1.2 Features n...

Amol Desai

• Feb 3rd, 2017

Following points we are taking into the consideration while writing down the test plan. Objective Introduction Assumption and Test Approach Entry Criteria Exit Criteria Resumption Criteria...

Answer Question  Select Best Answer

What will you do when developer rejects your defect?

Piyush Patwa

• Nov 20th, 2017

If developer rejects the Bug. Follow the same steps with which the Bug was reproduced earlier. The bug verification should always be performed once before closing the Bug and if you come across the sa...

B reddy

• Jul 23rd, 2014

If the raised defect is not related to that developer he will reject the defect.

Answer Question  Select Best Answer

bug Number 1=Severity 1 & priority 3,
Bug Number 2=severity 3 & priority 1,
(high=1,Medium=2,Low=3)

Charles Keche

• Feb 1st, 2018

Severity always applies to business impact while Priority is the impact to test progression..so the business e.g. BA or Product owner will determine the severity while the test assigns the priority according to how many test scripts are being affected or blocked.

hash

• Dec 16th, 2014

I agree with Niyati, Priority will be decided by business. Business may say they would want a defect to be fixed first and that might not have SEV1 from tester perspective. Priority is the order in which business wants to get the defects fixed

Answer Question  Select Best Answer

If at all 3 testers of a teem found same defect how to remove duplicate bugs

MAHESH GUNDU

• Apr 20th, 2018

Using peer-review... we can eliminate the duplicate bugs

Suma

• Apr 22nd, 2012

First of all we should not raise the defects again, which already raised by other tester. Before raising any defect we should check other defects in that particular module, release is any other tester...

Answer Question  Select Best Answer