Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
A tool used to track the defect/issues/concerns logged by tester. This is very much required in any testing
environment.Some common features of any bug tracking tool allow you to priortize the defects ,keep track of
bug status (like open/close/verified) ,date logged etc..
This is also a Software Application that helps the Test team in end-to-end Defect Life Cycle Management. The
advantage of this tool is that all the stake holders of the Testing Project can keep track of the latest Status of all
the Bugs logged in by the Test team.
Also, it will be help in the following:
2. Generating a variety of Bug reports such as Daily & Weekly and also Application wise and Module wise Bug lists.
3. Also the tool can be configured for sending automated mail messages to all the concerned people whenever a
Bug is logged in the tool and change occurs to the same.
4. Some tools have more features such as generating Graphical reports based on the Bug Data.
Validation ensures that functionality, as defined in requirements, is the intended behavior of the product;
validation typically involves actual testing and takes place after verifications are completed
Verification is a process in which information is checked using accurate measures. E.g. when you enter a new
password you are asked to retype it to verify that the password supplied is correct.
Validation however is the automatic process in which rules are applied in order to make information correct,e.g.
if the right type of data is entered in a certain cell in a database.
TestPlan is an roadmap to acheive your testing activity.ie what are the process that u are going to follow in ur
testing.
5.stress testing?
Just try some extreme conditions for your system : unplug the net cable, shut down the DB Server, kill a running
process of the system,.
Stress testing is subjecting the system under
heavy load but, denying the required resources for the system to perform (like RAM,Disc..etc).
Even if the system fails, it is not cause of worry.
The Idea is basically to confirm that the system does not fail in Improper manner.
The system should not Corrupt the data / Lose the existing data when it Fails.
Driver: A piece of code that passes test case to another piece of code.
Stress testing is stressing beyond maximum limits - focus is to know failure behavior of the system.
Load Testing is a process to check where exactly the system/server starts to degrade.
Stress testing is negative testing.eg.if a system can response properly for say 100 users.Bulk of users will be
accessed to check the systems performance,there by reducing the no. of users if the system degrades.
Defect :Is an error found AFTER the application goes into production
Error : Deviation for actual and the expected/theoritical value .
Bug : An Error found in the development environment before the product is shipped to the customer .
Defect : An Error found in the product itself after it is shipped to the customer .
10.What weaknesses within a computer network can have direct effect on the functionality of the system
The weakness may be from server to installation and unavalaiability and inability to retrieve the required
data or files to the system
test plan: A record of the test planning process detailing the degree of tester indedendence, the test
environment, the test case design techniques and test measurement techniques to be used, and the rationale for
their choice.
test case: A set of inputs, execution preconditions, and expected outcomes developed for a particular objective,
such as to exercise a particular program path or to verify compliance with a specific requirement. After
[IEEE,do178b]
Test: The process of executing the system satisfies specific requirements and detecting the errors
Test Plan: Test Plan is a document which gives object,scope,and focus software testing efforts.
Test case: Test case is a document which gives action,event expected results in future that object perfectly
working or not.
Verification
============
- Here we will determine that the Work Products of a given phase of a Software Development Life Cycle, meets
the requirements established in the previous phase.
- We will also see that the work is complete, correct and consistent enough to support the next phase.
Validation
==========
- It is the process of evaluating the Software throughout the Software Development Life Cycle to ensure
compliance to requirements.
- Here we will see that the Actual Results are in conformance with Expected Results when subjected to
anticipated events.
- Under the given operational conditions the Systems behaves as per the Users Expectations.
There is no standard that bug life cycle should have the above stages. You can define your own sub stages
according to your convenience
16. What is test case management? How can effective test cases be written?
Test Case Management is nothing but maintaining the test cases with a process in a storage medium which can be
anything from CVS/RCS database txt file etc.
Any product company would have a defined process and management to maintain their huge numbers of
testcases.
The TC Management also have procedural guidelines to the users while recording the testcases.
Software Project is done for a specific clients of your company. For this some of the testing may be done at
client's side. For example, Acceptance Testing..
Software Product is not done for a single client and it is released as a product of the company.
Application is more specific for a particular business requirement where as product is more generic.
In other words, application is used for solving particular problem or specific need, where as product looks at
broader sense.
Requirement Phase:
When you build an application you look at particular user/client and understand their requirements. But for
building a product the requirements are gathered not by looking at a single user but one does market survey and
come up with most likely features that cross section
of users will look at.
These requirements are not only functional requirements but also platform/hardware requirements.
Typically product offers set of features then it's up to the organizations to use some or all of them.
In some cases Product don't have all the required features, in such case it is customized to suite the need, in
such case this implementation/customized version of product can be considered as
application.
Testing:
Typically application is supported on single platform, the one that target organization has. For products it's
variety of OS, hardware etc, you must have see typically product matrix. Hence it is necessary to test the
product on all the combinations.
Releases:
Though it is not completely true but in most cases, once application is developed there are few enhancements.
Also bug fixes are typically completed before User Acceptance testing. Since for product there is not a single
customer, there is no UAT as such, once QA certifies product is released to market. Very fact that product is
generic and is suppose to work in different scenarios it's very difficult to exhaust all the scenarios during QA
testing, and as you know the defects are found in released product. The bug fixes for these are handled by patch
releases (Microsoft is very good example for these patch releases, you must have seen SP1, SP2 etc even for OS).
This means configuration management is complex for Products.
Otherwise rest of the software lifecycle stages like specs, development, impact analysis are identical.
System testing is a serious of different test who's primary purpose to execute the system fully exercise computer
based system.each test have different purpose it will work,and properly integrating and allocating fuctions
Testing involves operation of a system or application under controlled conditions and evaluating the results (eg,
'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The
controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt
to make things go wrong to determine if things happen when they shouldn't or things don't happen when they
should. It is
oriented to 'detection'
20. Basis path testing: To execute every statement in a program at least one time.By using basis path test will
find out the execute path of the statement
Data Flow testing: select statement in a program and uses the variable of the definition
22.Regression test
Regression test is nothing about Retesting the test which is already executed to compare the actual result with
expected result after fixing the bug/
24.TEST CASE
Test Case
=========
Test cases should be designed and developed based on the User requirements and System architecture and
Functionality.
Also this varies based on what testing and at what stage the testing is carried out.
If it is Unit Testing then the Test Cases will be developed to test the smallest part of the overall user's
requirements or the small component of the overall system architecture.
If it is an Integration testing then the Test case will be developed to verify a function of the User requirements or
an interface between two modules of the System.
If it is a System Testing then the Test Case will be developed to validate the System as a whole End-to-end, while
combining it with the required HW, Database, Networking and any other connections such as Printers, Fax or any
other external supporting SW application. Here, while an input is given to the System, the System's behavior to
handle the input data and its final expected out put will be verified.
And finally if it is User Acceptance Testing, then the Test Cases will be developed from the User's requirements
perspective.
Sanity Testing
=============
Test case: test case is a document which describes action,event,expected result,in future that object is perfectly
working or not.
Test case should be developed based on to the input requirement,and to check that object perfectly working or
not.
Test plan: Test plan is a document which describes object,scope and focus on the software testing efforts.
Test plan should be developed whenever requirement is getting at the time test plan should developed.
Sanity testing: sanity testing is a cursor testing it is performed whenever the cursor testing is sufficient to prove
the application is functioning according to the specification.
Verification: verification refers set of activities that ensure built into traceable to the customer requirement.
Validation:Validation refers different set of activities that ensure software is correctly implement or not.
Depends on the software being tested, the purpose of the software, and the complexity of the software. The
time of year can also affect the testing phase (software often has its testing time cut in November-December in
order to have the software available for Christmas).
On-line Games, for example, are very complex and difficult to make. Testing can sometimes take around a year.
Simple word processors may take a week to test, however. It all depends on how many things can go wrong (the
more complex, the more things to test). It's always possible that testing times will get cut short, as well.
Furthermore, it's impossible to find every bug in the program no matter how much testing you do. In that sense,
the testing phase never really ends.
26.tell me about v model
'V' shape model describes about the process about the construting the application at a time all the Analysing,
designing, coding and testing will be done at a time. i.e once coding finishes it'll go to tester to test for bugs if
we got OK form tester we can immediately start coding after coding again send to tester he'll check for BUGS and
will send back to programmer then he,programmer can finish up by implementing the project.
it is the model what is using by most of the companies.
Test Director is a management tool that gives systematic control over the testing process.
if your using win runner,you can integrated to test director by using tools menu you can click test director
command,otherwise you can going directly to test director you can built the automated tool which you want to
use.
the orderly areanging the e-learning process by the way of some rules& regulations are predefined are verified
and to validate the task
29.what is traceability phase matrix?were it has been used and what is need for it?
It can be used to trace the functionality of the module. It is created before writing the test cases. Then the test
case ids can be added
Typically, in test situations, traceability matrices are used to trace requirements to test cases in order to ensure
that there are test cases for all the requirements. Some tools, such as Rational Suite Enterprise, will help
analysts trace requirements and then allow the tester to trace from the use cases and/or requirements to test
cases.
Of course, many types of traceability matrices may be created or reverse engineered. For example, you may
back trace defects-->test cases-->use cases and vice versa. The default term likely applies to tracing
requirements to test cases though
30.what is the difference between REGRESSION TESTING AND RETESTING. Why regression testing is vital in object
oriented programing
after retesting only we can for regression testing.
retesting is the process of testing of application after fixing the bugs.
regession testing is the process of reexecuting the application whether it affects the other parts of application or
not.
Regression testing is verifing that previously passed tests are still OK after any change to the software or the
environment, usually to verify that a change in one area doesn't affect other or unrelated areas. Retesting? just
running the same tests and conditions over and over again, to verify reproducability (precision)
Using the Traceability Matrix we will be able to confidently say that all the User Requirements are properly
documented and respectively addressed well in the following also:
1. Regression testing
3. Batch testing
36. BlockBoxTest: Testing process is done without knowing internal process is BlockBox testing
WhiteBox Test: Testing process is done with knowing internal process is whitebox testing
37.Describe the fundamental difference between Quality Assurance and Quality Control?
quality assurance meant for developing,organising the best quality process.
quality control meant for implementing the process developed by former team
seviority is assigned based on the impact on the risk.The risk may be human life or huge amount of money
business specific. example
If a bug in financial application wrong calculation of interest which may cause the bank to suffer huge financial
losses(legal and may need the bank to close) then sevority is given as 1 (highest) and need to be fixed.the bug
may be related to printing first name first and last name second.which willl have less impact on the business
seviority is less say 4.
Priority comes when we are fixing the bug which one needs to be taken first for fixing.This decision is taken by
the schedule of the project.
If you take the above case if additional information is required for interest calculation and the delivery got
enough time then priority can be given to less seviority bug then high seviority bug
40.A bug is raised by the tester and it was told that it is not a bug by the programmer. What to do?
Its a tester who has to say if that is a bug..a programmer would never accept it a bug though in all probability he
would sneakily fix it. The tester needs to take a call. If there is a disagreement by the programmer after posting
the bug, then he should discuss it through the manager
Backend testing seems to be used to refer to any number of things such as white box testing, or simply lower
level testing sans GUI if applicable.
These terms aren't formalized and should not be used in test plans. Refer to a good template to find the proper
terms to use in place of "front-end" and "back-end" testing
43.What is the difference between user acceptance testing and beta testing
By User acceptance testing we mean validating
whether all the user requirements specified in SRS is met after code freeze. Beta Testing is done at 90-95% of
code freeze. Any modifications to be done at this stage is a high level decision
47.What is testing? __
Testing is the process of identifying defects, where a defect is any variance between actual and expected results
Write bug reports immediately; the longer you wait between finding the problem and reporting it, the more
likely it is the description will be incomplete, the problem not reproducible, or simply forgotten.
Writing a one-line report summary (Bug's report title) is an art. You must master it. Summaries help everyone
quickly review outstanding problems and find individual reports. The summary line is the most frequently and
carefully read part of the report. When a summary makes a problem sound less severe than it is, managers are
more likely to defer it. Alternatively, if your summaries make problems sound more severe than they are, you will
gain a reputation for alarmism. Don't use the same summary for two different reports, even if they are similar.
The summary line should describe only the problem, not the replication steps. Don't run the summary into the
description (Steps to reproduce) as they will usually be printed independently of each other in reports.
Ideally you should be able to write this clearly enough for a developer to reproduce and fix the problem, and
another QA engineer to verify the fix without them having to go back to you, the author, for more information. It
is much better to over communicate in this field than say too little. Of course it is ideal if the problem is
reproducible and you can write down those steps. But if you can't reproduce a bug, and try and try and still can't
reproduce it, admit it and write the report anyway. A good programmer can often track down an irreproducible
problem from a careful description.
The most controversial thing in a bug report is often the bug Impacts: Low, Medium, High, and Urgent. Report
should show the priority which you, the bug submitter, believes to be appropriate and does not get changed.
Bug Impacts __________________________________________
Low impact
This is for Minor problems, such as failures at extreme boundary conditions that are unlikely to occur in normal
use, or minor errors in layout/formatting. These problems do not impact use of the product in any substantive
way.
Medium impact
This is a problem that a) Effects a more isolated piece of functionality. b) Occurs only at certain boundary
conditions. c) Has a workaround (where "don't do that" might be an acceptable answer to the user). d) Occurs
only at one or two customers. or e) Is very intermittent
High impact
This should be used for only serious problems, effecting many sites, with no workaround. Frequent or
reproducible crashes/core dumps/GPFs would fall in this category, as would major functionality not working.
Urgent impact
This should be reserved for only the most catastrophic of problems. Data corruption, complete inability to use
the product at almost any site, etc. For released products, an urgent bug would imply that shipping of the
product should stop immediately, until the problem is resolved.
Application Usability:
Appearance an outlook (Placement an alignment of objects on screen)
User Interface Test (open all menus, check all items)
Basic functionality checking (File+Open+Save, etc..)
Right mouse clicking sensitivity
Resize/min/max/restore app, windows (check min app size)
Scrollability when applicable (scrollbars, keyboard, autoscrolling)
Keyboard and mouse navigation, highlighting, dragging, drag/drop
Print in landscape an portrait modes
Check F1, What's This , Help menu
Short-cut and Accelerator keys
Tab Key order and Navigation in all dialog boxes and menus
Basic compatibility:
16 bit OS (Win 3.x, Win95, OS/2, WinNT3.x)
32 bit OS (Win95, Win98, Win200, WinNT4.x) UNIX
1. Try to break up your huge application into modules that are functionally independent.
2. Within each module you start with the functions one by one.
3. For a simple function write all possible test cases that arise to be tested, while using the application as there
are no specs.
4. In this way you could complete one function and in turn whole application.
5. To prepare test cases or plan make use of Excel sheet. Each sheet will define each function within the module.
This is best way to organize the test cases.
11:14 PM