Test Strategy:
Scope & Objective: About need for testing in our organization
Business Issues: Budget Controlling for testing
Test approach: defines the testing approach between development stages and testing factors.
Test environment specifications: Required test documents developed by testing team during testing.
Roles and Responsibilities: Defines names of jobs in testing team with required responsibilities.
Communication & Status Reporting: Required negotiation between two consecutive roles in testing.
Testing measurements and metrics: To estimate work completion in terms of Quality Assessment, Test management process capability.
Test Automation: Possibilities to go test automation with respect to corresponding project requirements and testing facilities / tools available.
Defect Tracking System: Required negotiation between the development and testing team to fix defects and resolve.
Change and Configuration Management: required strategies to handle change requests of customer site.
Risk Analysis and Mitigations: a Common problem appears during testing and possible solutions to recover.Training plan
Tuesday, December 18, 2007
review of plans?
Review Test Plan
After completion of test plan writing test plan author concentrate on review of that document for completeness and correctness. In this review, selected testers also involved to give feedback. In this reviews meeting, testing team conducts coverage analysis.
After completion of test plan writing test plan author concentrate on review of that document for completeness and correctness. In this review, selected testers also involved to give feedback. In this reviews meeting, testing team conducts coverage analysis.
contents of test plan?
Prepare Test Plan
Format:
1) Test Plan id: Unique number or name
2) Introduction: About Project
3) Test items: Modules
4) Features to be tested: Responsible modules to test
5) Feature not to be tested: Which ones and why not?
6) Feature pass/fail criteria: When above feature is pass/fail?
7) Suspension criteria: Abnormal situations during above features testing.
8) Test environment specifications: Required docs to prepare during testing
9) Test environment: Required H/w and S/w
10) Testing tasks: what are the necessary tasks to do before starting testing
11) Approach: List of Testing Techniques to apply
12) Staff and training needs: Names of selected testing Team
13) Responsibilities: Work allocation to above selected members
14) Schedule: Dates and timings
15) Risks and mitigations: Common non technical problems
16)Approvals: Signatures of pm/qa/ etc
Format:
1) Test Plan id: Unique number or name
2) Introduction: About Project
3) Test items: Modules
4) Features to be tested: Responsible modules to test
5) Feature not to be tested: Which ones and why not?
6) Feature pass/fail criteria: When above feature is pass/fail?
7) Suspension criteria: Abnormal situations during above features testing.
8) Test environment specifications: Required docs to prepare during testing
9) Test environment: Required H/w and S/w
10) Testing tasks: what are the necessary tasks to do before starting testing
11) Approach: List of Testing Techniques to apply
12) Staff and training needs: Names of selected testing Team
13) Responsibilities: Work allocation to above selected members
14) Schedule: Dates and timings
15) Risks and mitigations: Common non technical problems
16)Approvals: Signatures of pm/qa/ etc
approch:?
Test approach: At which phase what type of testing
Mapping between test factors and development phases
Mapping between test factors and development phases
test casedesign?
Test case design: There are 3 types of designs
Ø Business logic based test case design
Ø Input domain based test case design
Ø User interface test case design
Ø Business logic based test case design
Ø Input domain based test case design
Ø User interface test case design
scope?
Scope: Scope is nothing but what is to be tested, to which extent application is tested, what is not to be testedObjective: what is the objective of the testing
wht is system study?
System study: We will study the application based on the following factors
1. Domain of the application
2. Software
1. Front end
2. Back end
3. Hardware
4. No of lines of code
5. 1 F.P= 10 lines pf code
6. No of screens
7. No of modules
1. Domain of the application
2. Software
1. Front end
2. Back end
3. Hardware
4. No of lines of code
5. 1 F.P= 10 lines pf code
6. No of screens
7. No of modules
what is STLC?
STLC: Software Testing Life Cycle
This starts at early phase when the bussiness requirement document is done, along with developing lifecycle by developers and stlc by testing team.
1..System study
2.Scope
what is the scope of testing for this application, it may differ to application to application
3.Approach
what are the testing approches whhich we are going to follow.this also varies from application to application.
4.Objective:
The main objective of testing which is carried out for this application.
5.Test planning : which throughs light on
what to test?
when to test?
who to test?
How to test?
6.Test case design :
how the requirements are cut down to Functionalities
How the functionalities are cut down to Scenarieos
how scenarieos are further divided in to or split in to testcases and
how test cases are then further designed to micro level by means of steps.
7.Test case review
Are the requirements are all covered
Are the scenarieos cover all the function points of requirement
Are all the test cases covered for each scenarieo
Are all the steps for test care are covered with out creating any ambigvity for the tester /customer while executing them.
8.Test case execution :
Executing test step by step to cover test case
Test case by test case to cover the Scenarieo
Scenario by scenarieo to cover the funtionality
This is repeated to cover all the functinalities.
9.Defect handling
If the actual is equal to Expected then test case is passed.
if not then there is need to raise the defect for the step which it is failed with providing information by means of snap shots or Error log's .
10.Gap analysis
If any gaps we can suggest to improve them
11.Deliverables
all the documents which we maintain from the Start of STLC till now.
This starts at early phase when the bussiness requirement document is done, along with developing lifecycle by developers and stlc by testing team.
1..System study
2.Scope
what is the scope of testing for this application, it may differ to application to application
3.Approach
what are the testing approches whhich we are going to follow.this also varies from application to application.
4.Objective:
The main objective of testing which is carried out for this application.
5.Test planning : which throughs light on
what to test?
when to test?
who to test?
How to test?
6.Test case design :
how the requirements are cut down to Functionalities
How the functionalities are cut down to Scenarieos
how scenarieos are further divided in to or split in to testcases and
how test cases are then further designed to micro level by means of steps.
7.Test case review
Are the requirements are all covered
Are the scenarieos cover all the function points of requirement
Are all the test cases covered for each scenarieo
Are all the steps for test care are covered with out creating any ambigvity for the tester /customer while executing them.
8.Test case execution :
Executing test step by step to cover test case
Test case by test case to cover the Scenarieo
Scenario by scenarieo to cover the funtionality
This is repeated to cover all the functinalities.
9.Defect handling
If the actual is equal to Expected then test case is passed.
if not then there is need to raise the defect for the step which it is failed with providing information by means of snap shots or Error log's .
10.Gap analysis
If any gaps we can suggest to improve them
11.Deliverables
all the documents which we maintain from the Start of STLC till now.
What will you consider during installation testing and who will do this?
The following points to be considered during installation testing.
1. Our set up program is properly working or not?
2. Easy interface, less navigation
3. Memory occupied after installation
4. Attempt to install the application on the older version of the application
5. Try to uninstall the application
6. Try to install the application on the current version of the application.
7. Is application is installing as per the installation guide
Generally release engineers will do this type of testing
They will also check the compatibility on the client side software’s
1. Our set up program is properly working or not?
2. Easy interface, less navigation
3. Memory occupied after installation
4. Attempt to install the application on the older version of the application
5. Try to uninstall the application
6. Try to install the application on the current version of the application.
7. Is application is installing as per the installation guide
Generally release engineers will do this type of testing
They will also check the compatibility on the client side software’s
Inspection:?
it is a formal meeting. In the group everyone have the source documents and they will check with their own mindset.
It is a formal meeting for verifying the code to find the defects as per the specifications
It is a formal meeting for verifying the code to find the defects as per the specifications
Walkthrough:?
It is an informal meeting. Group with moderator will involve in this. Moderator having the document and everyone follows the same.
It is an informal meeting for verifying the code to find defects and to verify the coding techniques.
It is an informal meeting for verifying the code to find defects and to verify the coding techniques.
what is security testing?
Security Testing: It is the process by means of checking the software security loopholes or how easy to hack our appliction
1. Authorization (whether user is able to access the application or not?
2. Access Control (permissions to access specific functions)
3.Authentication (validating the user from server side)
4. Cryptography (Encryption and Decryption)
1. Authorization (whether user is able to access the application or not?
2. Access Control (permissions to access specific functions)
3.Authentication (validating the user from server side)
4. Cryptography (Encryption and Decryption)
what is performance testing?
Performance Testing:
1. Performance Evaluation
Request?
Responce?
Through put?
Hits per second?..etc
2. Load testing (on Expected load)
3. Stress testing (More than expected load)
4. Volume testing:
Data volume in a file.
how many files can be uploaded or downloaded
1. Performance Evaluation
Request?
Responce?
Through put?
Hits per second?..etc
2. Load testing (on Expected load)
3. Stress testing (More than expected load)
4. Volume testing:
Data volume in a file.
how many files can be uploaded or downloaded
what is functionality testing?
Functionality Testing:
Functionality testing or requirements coverage
1. GUI or behaviral testing
Graphical user interface and navigatinal testings
2. Input domain testing
Input data testing based on BVA and ECP
BVA: Boundary value analysis
Range and size
ECP:Equivalent class partition
valid data and in valid data.
3. Error handling testing
How the Error messages are managed at appropriate places and valid matter displayed in them
4. Back end testing
what we are entered in the front end is stored in back end and retriving the same.
5. Mutation testing
If any changes made is it showing the changes.
here we can say it as negetive testing.
6. Sanitation testing
un wanted fields or functionalities which create ambigvity for the user are checked
Functionality testing or requirements coverage
1. GUI or behaviral testing
Graphical user interface and navigatinal testings
2. Input domain testing
Input data testing based on BVA and ECP
BVA: Boundary value analysis
Range and size
ECP:Equivalent class partition
valid data and in valid data.
3. Error handling testing
How the Error messages are managed at appropriate places and valid matter displayed in them
4. Back end testing
what we are entered in the front end is stored in back end and retriving the same.
5. Mutation testing
If any changes made is it showing the changes.
here we can say it as negetive testing.
6. Sanitation testing
un wanted fields or functionalities which create ambigvity for the user are checked
what is usability testing?
Usability testing: Testing whether application is user friendly or not?
Testing the easiness of the application
User interface testing
Manual support testing
User interface testing:
1. Easy of use
2. Less navigation
3. Ease to operate
Manual Support testing: Context sensitive in user manuals
i.e. checking the people computer interaction
In Usability Testing we will test not only the interface but also we check the
User manuals and training material.
Testing the easiness of the application
User interface testing
Manual support testing
User interface testing:
1. Easy of use
2. Less navigation
3. Ease to operate
Manual Support testing: Context sensitive in user manuals
i.e. checking the people computer interaction
In Usability Testing we will test not only the interface but also we check the
User manuals and training material.
What type of testing will you perform?
Types of testing to be done in the system testing
1. Usability testing
2. Functionality testing
3. Performance testing
4. Security Testing
5. Recielence testing/Recovery testing
1. Usability testing
2. Functionality testing
3. Performance testing
4. Security Testing
5. Recielence testing/Recovery testing
What is system testing?
System testing:
it is followed by balckbox testing techniques
systemtesting is done on the finishedprogrames before delevary
concentrates on what is the whole functionality of the application?
system testing is done baced on custemor requirementsand SRS document
it is followed by balckbox testing techniques
systemtesting is done on the finishedprogrames before delevary
concentrates on what is the whole functionality of the application?
system testing is done baced on custemor requirementsand SRS document
What is Big bang testing?
It is a method where all modules have been approximately developed and tested when the coding of whole modules completed and tested collectivly
bottom-up approch?
Bottom-Up approach
1. Low level modules are combined into build
2. Develop driver for that build
3. Test that build
4. Do regression testing
Advantages:
1. Errors in critical modules at low level can be found early
2. No stubs
Disadvantages:
1. Major functionalities can be tested lately
2. Interface errors are discovered lately.
1. Low level modules are combined into build
2. Develop driver for that build
3. Test that build
4. Do regression testing
Advantages:
1. Errors in critical modules at low level can be found early
2. No stubs
Disadvantages:
1. Major functionalities can be tested lately
2. Interface errors are discovered lately.
What isTop-down approach ?
Top-Down approach:
1. We start testing from the main module with stubs for subordinate modules
2. Replace the stubs with sub modules
3. Replace one stub at a time with sub module
4. Test after each module is integrated
5. Do regression testing.
Advantages:
1. No drivers
2. We can test major functionalities as early as possible
3. Interface errors are discovered early
4. We have partially working model so we can demonstrate to the client
Disadvantages:
1. Stubs are needed
2. Errors in critical modules in low level are found lately
1. We start testing from the main module with stubs for subordinate modules
2. Replace the stubs with sub modules
3. Replace one stub at a time with sub module
4. Test after each module is integrated
5. Do regression testing.
Advantages:
1. No drivers
2. We can test major functionalities as early as possible
3. Interface errors are discovered early
4. We have partially working model so we can demonstrate to the client
Disadvantages:
1. Stubs are needed
2. Errors in critical modules in low level are found lately
What is incremental testing?
Continuous testing of application as new functionality is added.
There are 3 types of incremental integration testing
1. Top-down approach
2. Bottom-Up approach
3. Sandwich approach
There are 3 types of incremental integration testing
1. Top-down approach
2. Bottom-Up approach
3. Sandwich approach
What is Integration testing? What are the types of integration testing?
Testing combined parts of the application to determine if they ,together performing well.
These combined parts may be individual modules Testing the group of modules in the application is called integration testing .
Types of Integration testing:
1. Incremental testing
2. Non incremental testing
.
These combined parts may be individual modules Testing the group of modules in the application is called integration testing .
Types of Integration testing:
1. Incremental testing
2. Non incremental testing
.
Unit testing:
Testing a module in our application Or Testing a micro function is called unit testingThe following things are considered in unit testing Execution testing:1. Branch coverage2. Loop coverage3. Programming technique testing Operation testing :( Testing the application on its normal operating conditions) 1. Output testing (Verifying the output) 2. Compatibility testing Unit testing Approaches:Boundary value analysis: Testing the application with the data collected at the boundaries Equivalence partition: input data is divided into valid and invalid typeCause effective graphing: Dividing the input domain into classes and analysis is performed to determine which input cause which effectError guessing: Random conditions data used for testing
Types of testing
1. Static Testing (Inspection.Walkthrough, Review)2. Dynamic Testing (All types of testing techniques)
Why there is a need of testing
a) To prove there are defects
b) To prove there are no defects
c) To prove that application is running with the customer requirements
b) To prove there are no defects
c) To prove that application is running with the customer requirements
DEF OF TESTING:
The process of executing the program with an intent of finding defects in a pre defined ways and
Examine the behavior of application by executing on sample data sets and Verifing the Actual values and validating the Actuals with Expected behaviour of the application is called testing
Examine the behavior of application by executing on sample data sets and Verifing the Actual values and validating the Actuals with Expected behaviour of the application is called testing
CMM_LEVELS?
1.Inetial:
This is inetial level where organization is not following any standereds.
They r following "adhoc" process.
2. repeatable:
2nd stage,Basic management standerds r implimented here
and these are implemented at project level
a)S/W requirment management
b)project planning
c)prject trcking
d)quality assurence
e)config manegement.
3.Defined:
an unique processis implemented throughtout the organization
standerds are,
a)organization process defined.
b)organization process focused
c)s/w training process
d)s/w product engeneering
e)integrated s/w management
f)inter group co-ordination.
4.Manage:
here organization concept trade on quality measurement
a)quantitative management process
b)s/w quality control.
5.Optimizing:
here organization concept trade on conteneous process requirements
a)defect prevention
b)technology change management
c)process change management
This is inetial level where organization is not following any standereds.
They r following "adhoc" process.
2. repeatable:
2nd stage,Basic management standerds r implimented here
and these are implemented at project level
a)S/W requirment management
b)project planning
c)prject trcking
d)quality assurence
e)config manegement.
3.Defined:
an unique processis implemented throughtout the organization
standerds are,
a)organization process defined.
b)organization process focused
c)s/w training process
d)s/w product engeneering
e)integrated s/w management
f)inter group co-ordination.
4.Manage:
here organization concept trade on quality measurement
a)quantitative management process
b)s/w quality control.
5.Optimizing:
here organization concept trade on conteneous process requirements
a)defect prevention
b)technology change management
c)process change management
Wednesday, September 26, 2007
wht is CMM&ISO?
capability maturity model it has 5 stagesand its licence is given by defence academy (us) (software)
level 1:inetial;
level2:repeatable;
level3:defined ;
level:4:managed
internatinalstanderd organization given by switzerland govt(mostly for industries)
level 1:inetial;
level2:repeatable;
level3:defined ;
level:4:managed
internatinalstanderd organization given by switzerland govt(mostly for industries)
what is QC?
QC:quality control;this is a dynamic process in which all functionalities of project/application/product devoleped, are validated ,it starts after devoping the product/appl/project phace is completed.done mainly by inspections and black box techniqes to ensure it as bug free .
what is QA?
QA:quality assurance is the static process which involves in the whole life cycle of the project/product /application devoloping process.which is of measuring and monetering the process of devolopment at each and every stage of devoloping phace,mostly through reviews,walkthroughs..etc.
what is testing
testing is the process of checking the application/project /product with respect to fulfilment of all desired requirements and fruitfulness of it with respect to fuctionality/or expectations of the custemor/client to ensure the released / devoloped product/project/application is bug free.
Tuesday, September 25, 2007
Audit:
An independent inspection or assessment activity that verifies compliance with plans, policies, and procedures; and ensures that resources are conserved.
Audience Evaluation:
The ability to evaluate audience needs and develop appropriate presentation materials.
ANSI:
The American National Standards Institute, that is the organization that helps set standards and also represents the United States in international standards bodies.
Affinity Diagram:
A group process that takes large amounts of language data, such as a list developed by brainstorming, and divides it into categories.
Acceptance Testing:
Testing to ensure that the system meets the needs of the organization and the end user or customer (i.e., validates that the right system was built).
Acceptable Quality Level (AQL)
ANSI/ASQC Z1.4 (1981) defines AQL as “the maximum percent nonconforming (or the maximum number of nonconformities per hundred units) that, for purposes of sampling inspection, can be considered satisfactory as a process average.”
Subscribe to:
Posts (Atom)