Knowledge Share

Knowledge is NOT Power IMPLEMENTATION of knowledge is Power!!!
 
HomePortalGalleryCalendarFAQRegisterUsergroupsLog in

Share | 
 

 material3

View previous topic View next topic Go down 
AuthorMessage
Admin
Admin


Posts : 141
Points : 407
Reputation : 0
Join date : 2007-12-29
Location : Chennai

PostSubject: material3   Wed Mar 26, 2008 4:02 pm

Testing Terminology:
Test Strategy: it is a document and it specifies approach to be followed by testing team.
Test planning: it is a document and it specifies schedule of testing including work allocation. The test plan is an implemented form of test strategy document.
Test Scenario or test case tittles: It specifies a unique condition to be applied on build to validate with the help of test cases
Test Procedure: It is also a document and it specifies a step by step procedure to execute corresponding test case and that build. This procedure is also known as test script.
Test Log : it is also a document and it specifies the results of test cases after execute on build. Eg: password failed.
Error, defect and bug: A mistake in coding is called error. This mistake found by test engineers during testing is called defect or issue. This defect or issue accepted by developers to resolve it is called bug.
Regression testing : The re-execution of selected tests on modified build to ensure bug fix work and occurrence of side effects is called regression testing.
Tests



Related passed test

Failed Tests
Remaining Testing

Pass failed

Defect Developers
Report
Retesting and iterative testing : The re execution of test on same application build with multiple test data is called re testing or data driven testing.
System testing process:










Modified V model :
Requirements Gathering [BRS]


Analysis[SRS]


Design Test Initialization


Coding and unit Testing Test Planning


Integration Testing Test Design




Initial Build


Test Execution


Test Closure


User Acceptance Testing


Release and maintenance
In above development software process model, testing process is inserted with separate testing team. This separate testing team is only conducting system testing.
Test Initiation : in this stage , project manager or quality analyst is developing test strategy documents. This document defines an approach to be followed by testing team.
Components in test Strategy:
1. Scope and objective: The importance of testing in that project.
2. Business issues : budget control for a testing
Eg: 100 % project Cost


64% 36%
Development Testing
&
Maintenance
3. Test Approach : Selected list of test factors to be applied on build. This factor selection is depending on project requirements , scope of that requirements and risks involved in that companies.
4. Roles and responsibilities : The name of jobs in testing team and their responsibilities
5. Test Deliverables : The names of testing documents and their formats[IEEE 829].
6. Communication and Status Reporting : The required negotiation in between every 2 jobs in testing team.
7. Testing Automation and Testing Tools : Test automation and testing the possibility of test automation and availability of testing tools in that organization.
8. Defect reporting and tracking: The required negotiation in between the development team and testing team to resolve defects.
9. Risks and mitigation : The list of reasonable risks rised during testing and solutions to overcome
10. Change and Configuration Management : This concept maintains software development process deliverables w.r.t changes in requirements. Eg: SRS,H.L.Dís ,L.L.Dís , programs, test plans, test cases etc.
11. Testing measurements and matrices : The list of measurements and matrices
12. Training plan : The required number of training sessions for testing people to under stand project / customer requirements.


Test Factors: Every test factor defines a testing issue or a testing topic. In general ,15 testing topics are available in market to define a quality software. These 15 factors are not mandatory for every project system testing. The selection of required factors in that 15 factors, depending on requirements of that project , scope of the requirements and risks involved , future enhancement in that company
Testing Topics :
1. Authorization : validity of users to connect to application..
2. Access control : Authorities of valid users to user specific services in that software .
3. Audit Trail: An internal data generation w.r.t user operations.
4. Continuity of processing: Integration of project execution with out any dead lock.
5. Correctness : Meet customer requirements in terms of functionality
6. Coupling: co existence with other software application to share common resources.
7. Data integrity: out software is taking correct type and size of inputs.
8. Ease of use: user friendliness of that software .
9. Ease to operate : Easy to install and uninstall
10. Portable: Run on any platform or multiple platforms.
11. Performance: Speed of processing
12. Reliability: Recover from abnormal situation
13. Service levels : order of functionality
14. Maintenance : Whether our software product is long time serviceable to customer site people or not
15. Methodology : whether out testing team is following rules and standards while testing or not


Test factors vs testing Techniques
1. Authorization  Security Testing
2. Access Control  Security testing
3. Audit Trail  Functionality Testing
4. Continuity  Integration testing by developers
5. Correctness  functionality testing
6. Coupling  inter system testing
7. Data Integrity  Input Domain testing
8. Ease of Use  User Interface Testing and manual support testing
9. Ease of operate installation testing
10. Portable Compatibility testing and configuration testing
11. Performance Load testing , stress testing, storage testing and data volume testing
12. Reliability testing Recovery testing and stress testing
13. Service level Functionality testing
14. Maintainable compliance testing
15. Methodology  Compliance testing an organization have to follow complete standards and protocols

Quality software  Test Factors  Testing Techniques  Test Cases
Test Planning : After finalization of test strategy for a corresponding project, the responsible test lead category people are preparing system test plan and unit test plans. The test plan document defines what to test ? How to test ? when to test ? and who to test? To develop these test plan documents , test lead category people are following below approach



Testing team formation



Identification of Tactical
Risks


Test Plan Documents


Review Test plan documents


From the above approach test lead is preparing system test plan and then divides that plan into multiple modules or unit test plans.
Testing team formation : in general the test planning process starts with testing team formation. In this stage test lead is depending on below factors .
project size
Availability of Test Engineers
Test Duration
Availability of test environment resources.


Client / server , web, ERP  3 to 5 months of system testing
System software  7 to 9 months of system testing
Machine critical  12 to 15 months of system testing
Robotic approach
Satellite approach

Identification of tactical risks : After completion of testing team formation test lead is concentrating on risk analysis . eg:
Risk1 : lack of knowledge on that domain
Risk2: lack of time
Risk3: Lack of resources
Risk4: Delays in delivery
Risk5: Lack of communication in between testing team and development team
Risk6: Lack of documentation
Risk7: lack of development process
Risk8: lazyness of development
Back to top Go down
http://knowledgeshare.forumotion.com
 
material3
View previous topic View next topic Back to top 
Page 1 of 1

Permissions in this forum:You cannot reply to topics in this forum
Knowledge Share :: Testing :: MANUAL TESTING-
Jump to: