Quality Assurance:- Planned and systematic set of 
activities necessary to provide adquate confidence that 
Requirements are properly established.QA is responsability 
of entire team.

Quality Control:- QC is the process in which quality of the 
product/project is compared with applicable standards;and 
action is tacken if any nonconfirm is detected.QC is 
responsability of testing team.

QUALITY ASSURANCE:is a defective preventive method applied 
while the product is under process.generally it is done 
through out the development process.it is used for 
monitoring,measuring and improving the strength of 
development process.

QUALITY CONTROL:is a defect-detection and defect-correction 
method after the product is built.i.e it checks whether the 
product has met all the customer expectations after it is 
built.

QA is process oriented and Qc is product oriented.
QC comes after QA.
QA is defined as a set of activities designed to ensure the
development and maintaince state is adequate and to ensure
that the system will meet its requirements..
QC is defined as a set of activities designed to evaluate
the development of a working product.

Quality Assurance:
1.Concentrates on the process of producing the products.
2.Defect prevention oriented.
3.Usually done throught out the life cycle.
4.This is usually a staff function.
5.Examples-Reviews and Audits.

Quality Control:
1.Concentrates on specific products.
2.Defect-detection and correction oriented.
3.Usually done after the product is built.
4.This is usually a line product.
5.Example-S/W testing at various levels.
Reference:-Page29 in Software Testing & Principles(by
Srinivasan Desikan And Gopalaswamy Ramesh)

Based on the you are company followes project life cycel.

different companies follows different types of software 
development models,depending up on the size.In small and 
medium companies follows a clasic waterfall model lik 
model,in which testing is starts after development process 
is complets,some medium and big organizations follows V 
model lik model in which testing starts right from Business 
requirment documnet or SRS,and it will continue untill 
product relese.

as soon as possible when the requirement is getting

Based on the system requirement specificaiton(SRS) we will 
write the test cases and then starts testing.

It depend on the life cycle model of your company.
generally aafter preperation of the test cases they will be 
get approved from the client.
before starting the execution shake out will be done to 
check weather the build was done properly or not on the 
application
this is call as FFA.

Testing Starts "As early as Possible" in the development
life cycle.

Static testing or Review used to test the SRS, FS, TEST PLAN
etc.... 

Prabhu Subramanian
CSS India Pvt Ltd.

Actually testing starts from the requirement phase onwards.
Once the requirements are baselined(srs) then we will go 
for writing testcases.Execution of our tests will be 
started during the testing phase after the release of the 
build.

Testing should be start end of software development and
After prepare the test plan of the project

Seviarity will be fixed by Testers
Priarity will be fixed by Developers

Tester have the full control with assigning the "Seviarity" 
and "Priority" and developer will have the control with the 
Status of the defect like tester assigned as "New" 
or "Open" and only developer can change this status 
has "Resolved" or "Fixed" and again tester will retest the 
same and if it closed will close the defect else "Re-open".

Severity decided by tester & priority decided by Developer

seviarity is given by test engineer or tester.

priarity is given by the test lead.

serverity is decide by test engineer and priority by pm or 
client

If u found a splling worngly typed in the home page,it is 
not going to affect the functionality of the application u 
can still work on the application,in this case the 
seviarity is high,bcaz it is compani reputation problem so 
it is given high seviarity and it is not going affect any 
other part of functionality so low priarity. Correct me if 
i am wrong

high severiaty-- in any application the application will be 
crashed with mulitiple use any funcnality for ex add button 
use 200 times. the application will bw crashed so we can 
give high seveiority.low priarity.so there is no need to 
debug it rightnow u can debug it after some days.

Lowest seviriaty and Highest priarity.-- for ex the yahoo 
website spelling is mistake the spell is yaho . so here we 
can give high priarity.because it will affect the site 
name. so we have to give the quick priority. but here we 
can give low seviarity  .the spell change is not going to 
the application crash.

High Severity and Low Priority: If we have found a bug 
regarding any major functionality but at the instant if we 
had postphoned the work to furture then that Bug need not 
be fixed at this intant only. Thus this Bug comes under 
High Severity and Low Priority Bug.

Low Severity and High Priority: If you have found a bug 
that is regarding any Spelling Mistake. For Eg:- If we are 
woking on any application say regarding the HSBC. And if 
there is Tyno in HSBC then this won't affect the 
Functionality. But if there is any Client's Visit etc., 
then this Bug comes under the Low Severity and High 
Priority.

low level bug is also called as cosmetic bug. i.e if there
is change in the spelling or colour mistake then we call it
as low level bug. it will be having low seviority(s1). and
priority is p5(i.e before delivery we can fix the error)

Medium level bug : if there is any mismatch with the
expected and actual values then we call it as medium level
bug, here the seviority is s2. and priority is p4(i.e with
in a week)

High level bug: It is an unexpected error or output, and the
seviority is s3. and priority is p3(i.e with in 2-3 days)


very High or Major level bug: any fatal error or  the module
crashes while running the application we call it as high
level bug. Seviority is s4 and priority is p3(i.e with in a 
day)

Urgent or Critical bug: application crash, seviority is s5
and priority is p1(i.e it has to be fixed with in 2 to 3 
hours )

low severity & high priority: if there is a spelling 
mistake in the home page of the company web site then it is 
of high priority, because it lead to the bad reputation of 
the company name. it is low severity,because it is 
affecting the basic functionality of the site.

high priority & low severity: if we develop a site for 1000 
mailids & if those slots have been registered within first 
2 days then it is of useless for other than first 1000. 
hence it is high priority & it is low severity because it 
is as per its design.

hi
 Hi seviarity is assingned in case of system crash,and 
priority depends on urgancy of removing a defect. There can 
be a situation when u are doing some transaction say 
addition, if after continuous 10000 operations system 
crashes, then it is high seviarity but currently it is not 
showing any stopper to application,so we can assign low 
priority.

test scenario for login
Verify the login

Test Methodology:

 Where will the testing take place?-In which stage of SDLC 
testing actually starts
 
Who will perform the tests?-People/resurces involved in 
testing
 
How will you communicate with and involve participants?	-
Bug logging and tracking
 
How will you schedule the testing?- Test scheduling
 
How will you manage application problems?-Risk management
 

Testing Methodology is nothing but the way we are 
implementing the testing principles.

Test strategy:

Test strategy gives information about critical test types 
performed during the lifetime of a project.
It is a company level document prepared by the QA people. 
Test strategy is a formal description of how a software 
product will be tested.
A test Strategy is developed for all level of testing.

To prepare test strategy test team first analyses the 
required test types of the 
application/product.

Generally test plan is a Sub-test strategy of the company 
level Test Strategy Document

test strategy means what type of testing following in our
current project this information contains in test strategy 
like Functionality testing , regression testing,smoke
testing ,lode testing....

Sorry sara test strategy is project related.
this is much more higher term,refers company process  that 
will follow for the testing.

rajendra prasad reddy

Test strategy is a testing approach to be followed by 
testing team in current project.
This test strategy consists of below components.
1.scope&objective
2.Business issues
3.Roles & responsibilities
4.communication &status reporting
5.Test responsibility matrix
6.Test automation &testing tools
7.Defect reporting &tracking
8.change & configure management
9.Risks & assumptions
10.Testing measurements &matrics
11.Training plan

Test startegy is an organisational level term which is 
applied for all the projects in the organisation.

generally the Test startegy consists of 
levels of testing
Types of testing
Test design techniques
configuration management
test metrics
terminology
Automation plan
List of automated tools

this is a company level document.the main aim of this 
project is test approaches to achieve test objectives.here 
test approache: means type of testing technique that are 
needed to testing of our app. build
test objective: means meeting customer business 
requirements before going for testing an app. build.

where the testing process is going on in the life cycle 
process. status of the process.

Instance means just creating a reference(copy).

This is related to OOPs based software white box testing.

Java or C++ will exhibit run time polymorphysm.
this means each object creates different instances at 
different times based on the requiremnts.

byee

rajendra

A widely used technique for securing computer systems is to 
execute programs inside protection domains that enforce 
established security policies. These containers, often 
referred to as sandboxes, come in a variety of forms. 
Although current sandboxing techniques have individual 
strengths, they also have limitations that reduce the scope 
of their applicability. In this paper, we give a detailed 
analysis of the options available to designers of 
sandboxing mechanisms. As we discuss the tradeoffs of 
various design choices, we present a sandboxing facility 
that combines the strengths of a wide variety of design 
alternatives. Our design provides a set of simple yet 
powerful primitives that serve as a flexible, general-
purpose framework for confining untrusted programs. As we 
present our work, we compare and contrast it with the work 
of others and give preliminary results. 

Vinodh Anandhan
Software Test Engineer
Bangalore
vinodhanandhan@gmail.com

Tread Testing testing means incremental component  
integration testing.
 it is whgite box testing technique.
This also called string test(string is a set of charecters).
In this development people first develop each compoent then
integrate each compoenent with other components untill the
full funcytionality of the application implemented.

byeee
Rajendra

12585