lakshmanaraj bg


{ City } mumbai
< Country > india
* Profession *
User No # 89319
Total Questions Posted # 0
Total Answers Posted # 65

Total Answers Posted for My Questions # 0
Total Views for My Questions # 0

Users Marked my Answers as Correct # 124
Users Marked my Answers as Wrong # 35
Answers / { lakshmanaraj bg }

Question { Metric Stream, 18069 }

Why you have chosen Testing as your career, not developer ?


Answer

Not only Developers, Testers also plays a lead role in all Software companies.

Because without tester's certification the product can not be launch.
Though developer develop the product, to release the particular product they need a tester.

so testers plays an important role.

But for a good tester, he need to write a coding..

In front of good testers, developers are nothing..

Is This Answer Correct ?    4 Yes 2 No

Question { 23355 }

What is Defect Seeding?


Answer

Defect seeding is the process of introducing known defect in the build which is ready to go for testing.

So developers knowingly introduce a defect, which will automatically occure after a certain time.

Purpose of defect seeding is to determine whether build is properly tested or not?

Is This Answer Correct ?    15 Yes 2 No


Question { Oracle, 15324 }

difference between validation and regression testing


Answer

Regression Testing:

The objective of regression testing is to ensure software remains intact.

A baseline set of data and scripts will be maintained and executed to verify changes introduced during the release have not “undone” any previous code.

Expected results from the baseline are compared to results of the software being regression tested.

All discrepancies will be highlighted and accounted for, before testing proceeds to the next level.

Validation:

Validation checks that the product design satisfies or fits the intended usage (high-level checking) – i.e., you built the right product.

This is done through dynamic testing and other forms of review.

The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements.

Is This Answer Correct ?    2 Yes 0 No

Question { 13494 }

Can u plz explan Agile Methodology? In testing how agile
methodology is used.


Answer

Agile Methodology:

Agile testing is used whenever customer requirements are changing dynamically.

If we have no SRS, BRS but we have test cases does you execute the test cases blindly or do you follow any other process.

Test case would have detail steps of what the application is supposed to do.

1) Functionality of application.

2) In addition you can refer to Backend, is mean look into the Database. To gain more knowledge of the application.

Is This Answer Correct ?    1 Yes 0 No

Question { CSC, 14528 }

what is difference between severity and priority


Answer

Priority is associated with scheduling, and severity is associated with standards.

Priority means something is afforded or deserves prior attention; a precedence established by order of importance.

Severity is the state or quality of being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles, e.g. a severe code of behavior.

The words priority and severity do come up in bug tracking.

A variety of commercial, problem tracking/ management software tools are available.

These tools, with the detailed input of software test engineers, give the team complete information so developers
can understand the bug, get an idea of its severity, reproduce it and fix it.

The fixes are based on project priorities and severity of bugs.

The severity of a problem is defined in accordance to the customer’s risk assessment and recorded in their
selected tracking tool.

A buggy software can severely affect schedules, which, in
turn can lead to a reassessment and renegotiation of priorities.

Is This Answer Correct ?    0 Yes 0 No

Question { 6050 }

What is defect management in QA?


Answer

Defect management in QA:

A process for analyzing and classifying defects and problem reports is an important part of defect tracking against quality targets.

The defect management process is based on the following general principles:

The primary goal is to prevent defects. Where this is not possible or practical, the goals are to both find the defect as quickly as possible and minimize the impact of the defect.

The defect management process should be risk driven -- i.e., strategies, priorities, and resources should be based on the extent to which risk can be reduced.

Defect measurement should be integrated into the software development process and be used by the project team to improve the process.

In other words, the project staff, by doing their job, should capture information on defects at the source.

It should not be done after-the-fact by people unrelated to the project or system

As much as possible, the capture and analysis of the information should be automated.

Defect information should be used to improve the process. This, in fact, is the primary reason for gathering defect information.

Most defects are caused by imperfect or flawed processes.

Thus to prevent defects, the process must be altered.

Is This Answer Correct ?    0 Yes 1 No

Question { Persistent, 7875 }

Explain 5 Test Matrics?


Answer

Test Matrics:

Measurement is fundamental to any engineering discipline.

Why Metrics?

- We cannot control what we cannot measure!

- Metrics helps to measure quality.

- Serves as dash-board.

The main metrics are: size, shedule, and defects.

In this there are main sub metrics.

Test Coverage = Number of units (KLOC/FP) tested / total size of the system.

Test cost (in %) = Cost of testing / total cost *100
Cost to locate defect = Cost of testing / the number of defects located.

Defects detected in testing (in %) = Defects detected in testing / total system defects*100.

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria.

Is This Answer Correct ?    3 Yes 0 No

Question { GrapeCity, 12161 }

Inspections, walkthroughs and Reviews comes under QA or QC?


Answer

walkthroughs:

It is the informal way of checking the documents.

A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

Review Roles:

Organisations will commonly have different named roles than those listed below, but this will give you an idea of a commonly used set of roles used throughout the world.

Manager:

The Manager will be the person who makes the decision to hold the review.

Managing people's time with respect to the review is also a Managers responsibility.

Moderator:

The Moderator effectively has overall control and responsibility of the review.

They will schedule the review, control the review, and ensure any actions from the review are carried out successfully.

Training may be required in order to carry out the role of Moderator successfully.

Author:

The Author is the person who has created the item to be reviewed.

The Author may also be asked questions in the review.

Reviewer:

The reviewers are the attendees of the review who are attempting to find errors in the item under review.

They should come from different perspectives in order to provide a well balanced review of the item.

Scribe:

The Scribe (or Recorder) is the person who is responsible for documenting issues raised during the process of the review meeting.

Inspections:

An inspection is a formal type of review.

It requires preparation on the part the review team members
before the inspection meeting takes place.

A person will be in charge of the inspection process,
making sure the process is adhered to correctly.

This person is called a Moderator.

The Moderator is normally a technical person by nature and may have Quality Assurance experience.

It is also suggested that the Moderator comes from an unrelated project.

This is to ensure an unbiased approach, and prevent a conflict of interests.

Is This Answer Correct ?    1 Yes 1 No

Question { nvidia, 9356 }

what is function testing?


Answer

Functionality testing of software is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.

Functionality testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

It's a type of GUI testing where functionality of an application is tested.

IN SIMPLE TERM:

Testing of all features and functions of a system [software, hardware, etc.] to ensure requirements and specifications are met.

There are many types of Functional testing.
they are following below,

1.functionality testing
2.Input domian testing.
3.Error Handling.
4.Database testing.
5.Object Property checking
6.Compatability testing
7.configuration testing
8.sanitation testing
9.Installation testing
10.Inter system testing.

Is This Answer Correct ?    1 Yes 0 No

Question { 4523 }

diff b/w alpha & beta testing? who will do this with
examples? can u pls help in this topics


Answer

ALPHA TESTING:

Alpha testing is conducted at the developers place, by the customer. The software is tested in a natural setting with the developer 'looking over the shoulder' of the user (i.e. customer) and recording errors and usage problems.
Alpha test are conducted in a controlled environment.

IN SIMPLE TERM:

Alpha testing: testing done by the developer side, here User’s are find the bug and developer has fixed it.

BETA TESTING:

Beta Testing is conducted at one or more customer sites by the end user of the software. Here the developer is not present during testing. Here the client tests the software or system in his place and recording defects and sending his comments to development team.
So the above is the detailed description about the System Testing.

IN SIMPLE TERM:

Beta testing: testing done by the Customer side.

Is This Answer Correct ?    1 Yes 0 No

Question { 10076 }

What Defect Density?


Answer

Defect density is one of the most important factors that allow one to decide if a piece of software is ready to be released.

One of the easiest ways to judge whether a program is ready to release is to measure its defect density—the number of defects per line of code.

Defect Density is the number of confirmed defects detected in software/component during a defined period of development/operation divided by the size of the software/component.

In theory, one can find all the defects and count them, however it is impossible to find all the defects within any reasonable amount of time.

Estimating defect density can become difficult for high reliability software, since the remaining defects can be extremely hard to test.

Defect seeding will work only if the distribution of seeded defects is similar to the existing.

DEFECT DENSITY FORMULA:

Defect Density = Number of Defects
_______________________
Size

USES:

1. For comparing the relative number of defects in various software components so that high-risk components can be identified and resources focused towards them.


2. For comparing software/products so that ‘quality’ of each software/product can be quantified and resources focused towards those with low quality.

Is This Answer Correct ?    0 Yes 0 No

Question { 5663 }

How many testcases should be there in one project or one
requirment?How many test case have you wrote in your last
project?


Answer

Its depend upon the project size.

Is This Answer Correct ?    1 Yes 0 No

Question { 3788 }

Description--->There are 5 modules in my application.
On every module there is a date box.
In 1st module, date box is used for 2
submenus.
My Question is ---> Should I have to write test cases for
date box for every modules & submenus?


Answer

Really that was a nice question...

of course, its ours(TESTERS) duty to write test cases for each and every module.

Though the developers develops the software, with out our testing part it won't go to customer hand.

Testers plays a important role in the modern IT companies.

Be a tester and test the world like any thing...

TESTERS are the Rockers, Sparkers and Makers..

Is This Answer Correct ?    1 Yes 0 No

Question { 9627 }

Give examples of boundary value and equivalence
partitioning test cases.


Answer

There are common mistakes that programmers make is that errors tend to cluster around boundaries.

For example, if a program should accept a sequence of numbers between 1 and 10,
the most likely fault will be that values just outside this range are incorrectly accepted or that values just inside the range are incorrectly rejected.

In the programming world these faults coincide with particular programming structures such as the number
of times a program loop is executed or the exact point
at which a loop should stop executing.

This works well with our equivalence partitioning idea because partitions must have boundaries.

A partition of integers between 1 and 99, for instance, has a lowest value, 1, and a highest value, 99.

These are called boundary values. Actually they are called valid boundary values because they are the boundaries on the inside of a valid partition.

What about the values on the outside? Yes, they have boundaries too.

So the boundary of the non-valid values at the lower end will be zero because it is the first value you come to when you step outside the partition at the bottom end.

At the top end of the range we also have a non-valid boundary value, 100.

This is the boundary value technique, more or less.

For most practical purposes the boundary value analysis technique needs to identify just two values at each boundary.

For reasons that need not detain us here there is an alternative version of the technique that uses three values at each boundary.

For this variant, which is the one documented in BS 7925-2, we include one more value at each boundary when we use boundary value analysis:
the rule is that we use the boundary value itself and one value either side of the boundary.

So, in this case lower boundary values will be 0, 1, 2 and upper boundary values will be 98, 99, 100.

What does ‘as close as we can get’ mean? It means take the next value in sequence using the precision that has been applied to the partition.

If the numbers are to a precision of 0.01, for example, the lower boundary values would be 0.99, 1.00, 1.01 and the upper boundary values would be 98.99, 99.00, and 99.01.

some example of Boundary Values:

1) The boiling point of water:
The boundary is at 100 degrees Celsius, so for the 3 Value Boundary approach the boundary values will be 99 degrees,
100 degrees, 101 degrees—unless you have a very accurate digital thermometer, in which case they could be 99.9 degrees, 100.0 degrees, 100.1 degrees.

For the 2 value approach the corresponding values would be 100 and 101.

2) Exam pass:
If an exam has a pass boundary at 40 per cent, merit at 60 per cent and distinction at 80 per cent the 3 value boundaries would be 39, 40, 41 for pass, 59, 60, 61 for merit, 79, 80, 81 for distinction.

It is unlikely that marks would be recorded at any greater precision than whole numbers.

he 2 value equivalents would be 39 and 40, 59 and 60, and 79 and 80 respectively.

Is This Answer Correct ?    0 Yes 0 No

Question { 4415 }

what is entry and exit criteria?


Answer

Entry Criteria:

1) Business Requirement is at least 80% complete and has been approve to date.

2) Technical design has been finalized and approved.

3) Development environment has been established and is stable.

4) Code development for the module is complete.

Exit Criteria:

1) Code has version control in place.

2) No known major or critical defects prevents any modules from moving to system Testing.

3) A testing transition meeting has be held and the developers signed off.

4) Project manager approval has been received.

Is This Answer Correct ?    1 Yes 0 No

Prev    1   2    [3]   4   5    Next