Test Management

Test Management means "Management of Tests" or "Managing the testing process".
Management of tests applies over the whole of the Software Development Life Cycle,
so a Test Management Tool could be among the first to be used in a project.

Test Management Tools
A test management tool manages the tests, from early in the project and then continue to be used throughout the project and also after the system had been released.

Test management tools are typically used by specialist testers or test managers at "system or acceptance" test levels.

Features of Test Management Tools

- Management of tests(keeping track of the associated data for a given set of tests, knowing which tests      need to run in a common environment, number of tests planned, written, run, passed or failed);
-Scheduling of tests to be executed(manually or by a text execution tools);
-Management of testing activities(time spent in test design, test execution, schedule, budget)
-Interfaces to other tools:
  .test execution tools(test running tools)
  .incident mangement tools
  .requirement management tools
  .Configuration management tools
- Tracebility of tests, test results and defects to requirements or other sources
-Logging test results
-Preparing progress reports based on metrics(quantitative analysis),such as
  test run and test passed;
  incidents raised, defects fixed and outstanding.

Test Management Tools help to gather, Organize and Communicate information about testing on a project.

Source(ISTQB).

**Test What Test Gold?**

The first thing to do to check if you have real gold is to look at it.

Look for particular signs that point to real gold??

VISUAL TEST

Inspect the piece for official markings.

 A stamp will indicate either fineness (1-999 or .1-.999) or karat (10K, 14K, 18K, 22K or 24K). A magnifying glass will make this easier. Gosh this is Static Testing

Possibly to look for

Counterfeit pieces can often have a marking that appears authentic; more testing may be needed either way.An older piece might not have a visible marking due to wear.

2.Look for noticeable discoloration. It is important to check for discoloration in areas that face constant friction (typically around the edges).

If the gold seems to be wearing off and showing a different metal beneath it, you probably have a piece that is only gold plated.

2.Look for noticeable discoloration DOES S/W posses COLOR Which Color then …........

It is important to check for discoloration in areas that face constant friction (typically around the edges).

If the gold seems to be wearing off and showing a different metal beneath it, you probably have a piece that is only gold plated.

BITE TEST

Bite down on your gold with moderate pressure. S?DLY YOU CANNOT BYTE S/W

2.Examine your gold for any markings

In theory, real gold will show indents from your teeth; deeper markings indicate purer gold.

This is actually not a recommended test, as you can damage your teeth. Not to mention that lead is even softer than gold and gold-plated lead will appear to be gold when you bite it.

Magnet Test

This is an easy test, but it’s not an all-encompassing or fool-proof way to determine whether your gold is real. Something as weak as a fridge magnet will not be useful, but stronger magnets that you can find in specialized hardware stores or in common objects such as women’s purse latches, children’s toys, or even in old unused hard drives will be strong enough to perform this test.

Density Test

Weigh your piece of gold. A jeweler can normally do this for you for free if you don’t have your own scale. You will need the weight in grams. S/W is not tangible.

Ceramic Plate Test

Find an unglazed ceramic plate to use. If you don’t have this, you can purchase a random piece of unglazed ceramic from a home improvement store.

Drag your item across the surface. A black streak means your gold is not real, whereas a gold streak indicates your item is genuine.
Nitric Acid Test

Place your piece of gold in a small stainless steel container.

Put a drop of nitric acid on your gold and watch for any resulting reaction to the acid.

A green reaction indicates your item is either a base metal or gold plated.A milk-colored reaction would indicate gold-plated sterling silver. If there is no reaction, you mostly likely are dealing with real gold.

After a test Software does'nt turn to any color.

Software is likely to be compared to gold both are the end result of hard toil, however anything of good quality would eventually go through rigorous testing process. 

Weightage for Foundation level ISTQB Exam

Hi folks,
The information below will surely help you guys to clear the ISTQB foundation level Exam.

The most important aspect of preparation is knowing the weightage for different chapters involved.

Here is goes :-

1. Fundamentals of testing -                                                   7 Questions

2.Testing through out the life cycle-                                       6 Questions

3.Static analysis-                                                                   3 Questions 

4.Dynamic test design techniques-                                         12 Questions

  

5.Test Management -                                                            8 Questions

6.Tools for test design                                                           4 Questions

Concentrate on chapters 4,5,and 1 to get a  good score.

Hope this information could  be helpful  to get ISTQB Certified 

All the Best Team Testers. 

Regards

Vijaya Lakshmi

SEVERITY AND PRIORITY

"SEVERITY "         AND          "PRIORITY"

SEVERITY: The impact that a given defect has on the

              system.

PRIORITY: It is defined as how fast a defect should 

              be resolved.

SEVERITY CAN BE OF FOLLOWING TYPES:

Critical: 

The defects which results in the termination of the system and if there is no other way to get the expected results then the severity is taken as critical.

Major: 

The defects which results in the termination of the system but we have an alternative way to get the excepted results, then the severity is stated as major.

Moderate: 

The defect which does not cause the termination of the system but gives the wrong data then the severity is taken as moderate.

Minor: 

The defect which does not cause the termination of the system and we can obtain the required results by just working on the defects such type of severity is stated as minor.

PRIORITY CAN BE OF FOLLOWING TYPES:

High: 

The defects which should be fixed immediately and if the application cannot be further used until we fix it then they are given as high priority.

Medium: 

The defects which can be rectified later in the program.

Low: 

The defects which have less impact then it is taken under low priority.

DIFFERENT SCENARIOS OF SEVERITY AND PRIORITY 

High Priority & High Severity: 

For example if we want to login into an bank application but if it shows an error then we can't move further, since it should be fixed immediately then it is taken as an high priority.

High Priority & Low Severity:

For example if we login into an bank application but the spelling of the bank is misspelled then it does not affect the functionality but it spoils the reputation of the bank.So the priority of fixing it will be high and the severity will be low.

High Severity & Low Priority: 

The scenario in which clicking a certain link in the application and it gets terminated because that link is rarely used by the user, here priority will be less. Clicking that link affects the functionality of the system so the severity will be high.

Low Priority and Low Severity:

It is the scenario in which if there are any spelling mistakes in the text of a paragraph in an application which is rarely read by the users .In this case both severity and priority will be low.


Post by :- Susmitha

Myths of Software Testing

What is a Myth?

Myth is a traditional story concerning the early history of explaining natural or social phenomenon or people.

 Myth 1:

Testing is too expensive:-

Testing is very expensive; it is a myth, whereas the fact is, during software development the cost for testing is less when compared to cost incurred due to maintenance or correction later. Since it is known that early testing in many aspects saves both cost and time. However, cost reduced without testing may lead to improper design of software application and a useless product may be the outcome.

 Myth 2:

Testing is time consuming:-

Testing consumes lot of time, it is a myth, whereas the fact is, during SDLC of testing are never a time consuming process, however fixing the error which are identified during proper testing, consumes more time but it is a productive activity.

Myth 3 :-
Testing starts only after the product is fully developed:-

Testing is started only after the product is fully developed, it is a myth, whereas the fact is, though testing depends on the source code, the reviewing and developing of test cases is independent from development of code. Incremental and Iterative models are examples for reducing dependency of testing on fully developed software.

 Myth 4:-

 Complete Testing is Possible

Exhaustive testing is possible, it is a myth, whereas the fact is, there is possibility of testing all paths by the team but occurrence of exhaustive testing is not possible. During software development life cycle there might be some scenarios that are never executed by test team or the client and may be executed once the project has been deployed.

 Myth 5: -

If software is tested, then it should be bug free:-

If Software is tested, then it must be free from bug, it is a myth, whereas the fact is that even a tester with excellent testing skills has tested the application, there is no one to say with absolute certainty that software application is 100% bug free. It is a common myth which most project managers, clients and management team believe in.

 Hence to become a good tester, he should have a good idea on myths, and how can that be helpful in testing the product successfully, as “quality” is that which matters at the end of the day.

Post by :- Geetanjali