![Page 4Classification: Restricted
White Box Testing (WBT)
• WBT is a method of testing Application’s internal structure i.e Program
code
• Number of test cases are dependent on code complexity
[More the execution paths, more are the test cases to ensure code coverage]
• Also called structural /glass box testing
• Test design phase begins once coding is done
• Metrics to measure the code coverage in white box testing are
1. Statement coverage - % statements executed by test cases
2. Decision coverage - % decisions(Yes and No both) executed by test
cases
3. Condition coverage - % of conditions (True and false both) executed
by test cases](https://image.slidesharecdn.com/day-6othertestingtypes-180811153335/85/Other-Testing-Types-4-320.jpg)
![Page 10Classification: Restricted
Database Testing
• Deals with finding defects in the database component of the application
• Testing includes checking of
- Data type and size validity
- Data Integrity test
- Stored Procedures
- Triggers
• Examples
- Adding data that does not fit the constraint [adding name more than 40
characters where column has character constraint of 40]
- Checking “On Update” trigger firing by updating data in database
- Testing of stored procedures to check the output and error handling](https://image.slidesharecdn.com/day-6othertestingtypes-180811153335/85/Other-Testing-Types-10-320.jpg)
Other Testing Types
- 1. Quality Assurance / Software Testing Training Other Testing Types
- 2. Page 2Classification: Restricted Agenda • Testing the code – WBT • Database Testing • UI Testing • Non Functionality Testiing • Class Assignment
- 3. Page 3Classification: Restricted Contents: • Testing the code and database - White Box testing techniques - Database testing • Testing the user interface - UI testing - Usability testing - Accessibility testing - Localization testing • Non functional system level testing - Performance testing (Load , Stress, Endurance, Volume) - Installation testing - Configuration testing - Compatibility testing - Security testing
- 4. Page 4Classification: Restricted White Box Testing (WBT) • WBT is a method of testing Application’s internal structure i.e Program code • Number of test cases are dependent on code complexity [More the execution paths, more are the test cases to ensure code coverage] • Also called structural /glass box testing • Test design phase begins once coding is done • Metrics to measure the code coverage in white box testing are 1. Statement coverage - % statements executed by test cases 2. Decision coverage - % decisions(Yes and No both) executed by test cases 3. Condition coverage - % of conditions (True and false both) executed by test cases
- 5. Page 5Classification: Restricted White Box Testing (WBT) Sample code: #Statements= 2 If (a>b || a>c) #Decisions = 1 Printf(“Number a”); #Conditions = 2 Coverage of Test case 1 a=5,b=4,c=2 Test case 2 a=1,b=3,c=2 Test case 3 a=3,b=4,c=2 Statement 1 Yes Yes Yes Statement 2 Yes No Yes Decision Yes(Result – true) Yes(Result - False) Yes(Result – true) Condition 1 Yes(Result – true) Yes(Result - False) Yes(Result - False) Condition 2 No Yes(Result - False) Yes(Result – true)
- 6. Page 6Classification: Restricted White Box Testing (WBT) It can be seen that • Only TC1 is sufficient for 100% statement coverage • TC1 and TC2 are needed for 100% decision coverage • TC1, TC2, TC3 are needed for 100% condition coverage www.mindsmapped.com
- 7. Page 7Classification: Restricted Advantage of White Box Testing (WBT) • Easy to determine which input data ranges to be used to test the application effectively • Logical mistakes in the code can be located quickly • It helps in removing the extra lines of code, which can bring in hidden defects www.mindsmapped.com
- 8. Page 8Classification: Restricted Challenges and Limitations of White Box Testing (WBT) Challenges • To cover all possible paths and decision is difficult in complex applications • The tester needs to have knowledge of code and internal architecture of application Limitations • Will never test requirements which are not implemented / coded • Large number of test cases might be needed to test even in case of small code/ implementation changes
- 9. Page 9Classification: Restricted Database Testing • Database - To organize, store and retrieve large amounts of data - Storage at central location, easier multi-access - Commonly used databases – RDBMS (Relational database Management Systems) - Data is stored in tables in the form of rows and columns - SQL is used to perform database operations www.mindsmapped.com
- 10. Page 10Classification: Restricted Database Testing • Deals with finding defects in the database component of the application • Testing includes checking of - Data type and size validity - Data Integrity test - Stored Procedures - Triggers • Examples - Adding data that does not fit the constraint [adding name more than 40 characters where column has character constraint of 40] - Checking “On Update” trigger firing by updating data in database - Testing of stored procedures to check the output and error handling
- 11. Page 11Classification: Restricted UI Testing • UI comprises of controls like textbox, text area, radio button, drop down, checkboxes etc • UI testing determines how user friendly the application is from look and feel perspective
- 12. Page 12Classification: Restricted User Interface (UI) Testing • Checklist for UI testing included - Checking of UI design template from consistency and appropriateness perspective – font size, background and foreground colour schemes, frames, header, footer - Checking tab sequence - Placement of controls i.e Alignment and Positioning - Consistent look of some control throughout application - Screen resizing option • Example where UI is a key - Applications interfacing with medical equipments displaying critical information and graphs - Advertising and shopping websites - Search Engines
- 13. Page 13Classification: Restricted Usability Testing • Done to check ease of use of an application • To determine how simple it is to understand and use application without anyone’s help • Checklist for usability testing includes: - Is the user getting guided within the application? - Is proper error message and adequate help provided to the user on incorrect steps? - Do new users understand the application usage quickly? - Is quick access provided to frequently used features? Examples for Usability - For a web site, is navigation within the web pages provided and is there a home page and logout link on every page - Check for use of correct icons and corresponding tool tips - Check for dropdown values being sorted correctly
- 14. Page 14Classification: Restricted Accessibility Testing • Objective is to check that the application is usable by people with disabilities - Physical disability Able to operate using only one hand , not able to see mouse or keyboard - Vision disability Poor vision, colour blindness, blindness - Hearing disability Not able to hear clearly or can not hear at all
- 15. Page 15Classification: Restricted Localization Testing • Globalization is a process of application design so that it can be adapted to different languages and regions without any change in the program and code • Localization is the process of adapting a globalized application to a particular culture / locale. It includes translation of the Application’s UI & graphics for a specific culture /locale • Localization testing includes checking of - Language translation and statement length fitment - Date format localization – European style: DD/MM/YY - Text direction – right to left or left to right - Language of text in graphics, messages - Addressing cultural aspects in screen design and language used
- 16. Page 16Classification: Restricted What is non Functional Testing • Testing of “how well application as a whole behaves” when it is exposed to real life working conditions • Based on the non – functional requirements specified in the requirements documents • Conducted after system’s functionality is tested , during system testing • Non functional testing includes: Performance, installation, configuration, compatibility, security
- 17. Page 17Classification: Restricted Performance Testing • Performance testing checks whether application provides stipulated output in stipulated time • Carried out after functional testing • Performance requirements of application include - Response time – How fast request is processed / served. Example: Time taken for search feature - Throughput – Number of transactions processed by an application per unit of time. Example: Number of telephone bills processed by billing application in an hour - Types – Load, Stress, Endurance, Volume - Tools – Load Runner, Rational Performance tester, Silk performer, OpenSTA
- 18. Page 18Classification: Restricted Load Testing • A load test is conducted to understand the behaviour of the system under a specific expected load • Load means number of multiple users accessing the application concurrently, mentioned in the SRS • Example, online shopping application will be used by thousand users at a time. These user load can further be divided into different tasks like - 600 users log in, browse and then log off - 250 users log in, add items to cart, check out log off - 150 users just log in without any subsequent activity • Load testing includes - Creates users virtually using tools to perform above actions - Check the response time
- 19. Page 19Classification: Restricted Endurance Testing • Determine whether system can sustain to a continuous expected load for a longer duration • Predefined load is applied for a longer period of time • Example to check on-line shopping application flooded with 1000 users throughout the day
- 20. Page 20Classification: Restricted Stress Testing • To evaluate the ability of an application to maintain a certain level of effectiveness under unfavourable conditions • Unfavourable conditions include - overload the existing resources with excess jobs - Load is applied beyond the specified limits Example, - Increase no of virtual users beyond the prescribed load - Running several resource-intensive applications in a single computer at the same time like flooding a server with useless e-mail messages
- 21. Page 21Classification: Restricted Volume Testing • Refers to testing an application with a huge amount of data and check its limitations • Tests are conducted once database is expanded to required size • Determine whether limits are acceptable to meet the organizations projected business processing • This type of testing is needed mainly for transactions processing systems capturing real time sales etc • Applications performance during database updates or data retrieval is checked with volume of data
- 22. Page 22Classification: Restricted Installation Testing • Verify that all the necessary components of the application are getting installed correctly • Identifies different ways in which installation procedure may cause errors • Needs proper documented installation procedure • Tests include - Checking successful installation of application as per installation procedure - How installer reacts when pre-requisites of hardware, software are not met - Checking all available installation types for eg typical, custom, complete etc - Are all the files installed in the respective folder? - Checking uninstallation or midway cancellation of installation process • Smoke testing can be conducted after installation to confirm correct installation
- 23. Page 23Classification: Restricted Configuration Testing • When an application is developed, it is designed to work for a particular configuration • Configuration testing is done to assess applications behaviour and performance on the range of hardware and software configurations for which it is designed • It may include different hardware, processors, operating system, peripherals
- 24. Page 24Classification: Restricted Compatibility Testing • Test application for the configurations for which it is not designed and check its compatibility • Testing will include checking application on - Different platforms - Database • Cross browser compatibility testing - Web applications are always tested on different famous browsers as users may use any - Checking is done for functioning of special controls and UI Tools: Browsershots, Browsera, Browsercam
- 25. Page 25Classification: Restricted Security Testing • Determines that an application protects data and maintains functionality access as intended - Protection against intrusion / hacking / data leakage • Necessary for applications having critical information handling or govt sites or military organizations, financial sites, brand conscious industries • If Application is not secured , it leads to - Loss of creditability with customers, business, reputation - Unauthorized access to sensitive information - Regulatory non – compliance • Tools : IBM Rational AppScan, HP Web Inspect, Web Scarab
- 26. Page 26Classification: Restricted Types of applications and testing types Desktop – single or limited users Desktop – product for large number of users Client - Server Web Installation @ @@@ @@ @ UI @ @@ @@ @@@ Usability @ @@ @@ @@@ Accessibility / Localization - @@ @ @@ Configuratio n @ @@ @@ @@ Compatibility - @@@ @ @@@ Performance - @ @@ @@@ Security - @ @@ @@@
- 27. Page 27Classification: Restricted RISK MANAGEMENT • Risk management is an important part of planning for businesses. The process of risk management is designed to reduce or eliminate the risk of certain kinds of events happening or having an impact on the business.
- 28. Page 28Classification: Restricted Continued…. • Risk management is a process for identifying, assessing, and prioritizing risks of different kinds. Once the risks are identified, the risk manager will create a plan to minimize or eliminate the impact of negative events. A variety of strategies is available, depending on the type of risk and the type of business. There are a number of risk management standards, including those developed by the Project Management Institute, the International Organization for Standardization (ISO), the National Institute of Science and Technology, and actuarial societies.
- 29. Page 29Classification: Restricted Risk Risk type Description Staff turnover Project Experienced staff will leave the project before it is finished. Management change Project There will be a change of organizational management with different priorities. Hardware unavailability Project Hardware which is essential for the project will not be delivered on schedule. Requirements change Project & Product There will be a larger number of changes to the requirements than anticipated.
- 30. Page 30Classification: Restricted Risk Risk type Description Specification delays Project & Product Specifications of essential interfaces are not available on schedule. Size under estimate Project & Product The size of the system has been under estimated. CASE tool under performance Product CASE tools which support the project do not perform as anticipated. Technology change Business The underlying technology on which the system is built is superseded by new technology. Product competition Business A competitive product is marketed before the system is completed.
- 31. Page 31Classification: Restricted RISK MANAGEMENT-Phases • Risk identification • Risk Analysis • Risk Planning • Risk Monitoring
- 32. Page 32Classification: Restricted Project Management • Management involve activities and tasks undertaken by one or more persons for the purpose of planning, coordinating and controlling activities of other in order to achieve objectives that could not be achieved by other acting alone. • The activities that are involved in management are called as management functions.
- 33. Page 33Classification: Restricted Continued…. • The people who are responsible for these efforts performs the functions. • Project management is a system of management procedure practices, technology, skill and experience that are necessary to manage a project.
- 34. Page 34Classification: Restricted Continued… • And a s/w project management is the important activity of planning, organizing, directing, motivating and coordinating a group of professionals to a complain software development it is the responsibility of the project manager to implement the activities with life cycle approach selected for the project.
- 35. Page 35Classification: Restricted Project Management • Project Staffing • Project Planning • Project Scheduling
- 36. Page 36Classification: Restricted Project Staffing • Project Staffing includes gathering the resources for the project in different hierarchy levels. • The staff should include various levels of resources with the expertise level to balance the team.
- 37. Page 37Classification: Restricted • Project budget may not allow to utilize highly – paid staff. • Staff with the appropriate experience may not be available.
- 38. Page 38Classification: Restricted Project Planning Plan Description Quality plan Describes the quality procedures and standards used in a project. Validation plan Describes the approach, resources and schedule used for system validation. Configuration management plan Describes the configuration management procedures and structures to be used. Maintenance plan Predicts the maintenance requirements of the system/ maintenance costs and efforts required. Staff development plan Describes how the skills and experience of the project team members will be developed.
- 39. Page 39Classification: Restricted Project Scheduling • Bar charts and Activity Networks • Scheduling problems
- 40. Page 40Classification: Restricted What is Quality? • Quality is “fitness for use” - (Joseph Juran) • Quality is “conformance to requirements” - (Philip B. Crosby) • Quality of a product or service is its ability to satisfy the needs and expectations of the customer
- 41. Page 41Classification: Restricted Deming’s Learning Cycle of Quality
- 42. Page 42Classification: Restricted Deming’s Learning Cycle of Quality “Inspection with the aim of finding the bad ones and throwing them out is too late, ineffective and costly. Quality comes not from inspection but improvement of the process.” Dr. W. Edwards Deming Founder of the Quality Evolution
- 43. Page 43Classification: Restricted QUALITY PRINCIPLES Quality - the most important factor affecting an organization’s long-term performance. Quality - the way to achieve improved productivity and competitiveness in any organization. Quality - saves. It does not cost. Quality - is the solution to the problem, not a problem.
- 44. Page 44Classification: Restricted SEI – CMM • Software Engineering Institute (SEI) developed Capability Maturity Model (CMM) • CMM describes the prime elements - planning, engineering, managing software development and maintenance • CMM can be used for • Software process improvement • Software process assessment • Software capability evaluations
- 45. Page 45Classification: Restricted • A maturity level is a well-defined evolutionary plan toward achieving a mature software process. Each maturity level provides a layer in the foundation for continuous process improvement. • In CMM models with a staged representation, there are five maturity levels designated by the numbers 1 through 5 • Initial • Managed • Defined • Quantitatively Managed • Optimizing
- 47. Page 47Classification: Restricted Level Focus Key Process Area Result 5 Optimizing Continuous Process Improvement Organizational Innovation and Deployment Analysis and Resolution Highest Quality /Lowest Risk 4 Quantitatively Managed Quantitatively Managed Organizational Process Performance Quantitative Project Management Higher Quality /Lower Risk 3 Defined Process Standardization Requirements Development Technical Solution Product Integration Verification Validation Organizational Process Focus Organizational Process Definition Organizational Training Integrated Project Mgmt Risk Management Decision Analysis and Resolution Integrated Teaming Org. Environment for Integration Integrated Supplier Management Medium Quality /Medium Risk 2 Managed Basic Project Management Requirements Management Project Planning Project Monitoring and Control Supplier Agreement Management Measurement and Analysis Process and Product Quality Assurance Configuration Management Low Quality /High Risk 1 Initial Process is informal and Adhoc Lowest Quality /Highest Risk