Testing in Information Systems

Week 6 : Ensuring Quality and Performance

Introduction to Information System Testing

​

What is Information System Testing?

Introduction to Information System Testing

​

What is Information System Testing?

System testing, also referred to as system-level testing or system integration testing,

​

is the process in which a quality assurance (QA) team evaluates how the various components of an application interact together in the full, integrated system or application

Introduction to Information System Testing

The main benefits of system testing:

​

Introduction to Information System Testing

The main benefits of system testing:

​

Improved Product Quality: System testing enhances product quality by ensuring it works across various platforms and environments.

​

Introduction to Information System Testing

The main benefits of system testing:

​

Error Reduction: It helps identify errors that might have been missed during earlier testing phases.

Introduction to Information System Testing

The main benefits of system testing:

​

Cost Savings: Early detection of defects through system testing saves time and reduces unexpected costs and delays, supporting improved control over spending.

​

Introduction to Information System Testing

The main benefits of system testing:

​

Security: makes sure there are no security gaps in the system, protecting data and users from potential damage.

​

Introduction to Information System Testing

The main benefits of system testing:

​

Customer Satisfaction: Provides insight into the product's stability at all development stages, boosting customer confidence and user experience.

​

Introduction to Information System Testing

The main benefits of system testing:

​

Easier Code Modification: Identifies coding issues during development, making it easier to modify code before it goes into production.

​

Introduction to Information System Testing

The main benefits of system testing:

​

Software Performance: analyzes changes in system performance (such as memory use, CPU utilization, and lag), enabling measures to avoid in a situation that performance falls..

Overview of Testing Types

​

Types of Testing in Information Systems

Unit Testing

​

Unit Testing: The Building Blocks

Unit Testing

​

Unit Testing: The Building Blocks

Integration Testing

​

Integration Testing: Connecting the Dots

System Testing

​

System Testing: The Big Picture

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Implement Prototyping in Acceptance Testing

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Develop a Functional Prototype: Create a prototype that is functional enough to demonstrate the key features and workflows of the final system.

Implement Prototyping in Acceptance Testing

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Develop a Functional Prototype: Create a prototype that is functional enough to demonstrate the key features and workflows of the final system.

Gather User Feedback: Conduct sessions where end-users interact with the prototype. Collect detailed feedback on various aspects like functionality, ease of use, and overall user experience.

Implement Prototyping in Acceptance Testing

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Develop a Functional Prototype: Create a prototype that is functional enough to demonstrate the key features and workflows of the final system.

Gather User Feedback: Conduct sessions where end-users interact with the prototype. Collect detailed feedback on various aspects like functionality, ease of use, and overall user experience.

Iterative Updates: Use the feedback to make iterative improvements to the prototype. This process helps in aligning the final product more closely with user expectations and requirements.

Implement Prototyping in Acceptance Testing

Acceptance Testing

​

Acceptance Testing: Meeting User Expectations

Develop a Functional Prototype: Create a prototype that is functional enough to demonstrate the key features and workflows of the final system.

Gather User Feedback: Conduct sessions where end-users interact with the prototype. Collect detailed feedback on various aspects like functionality, ease of use, and overall user experience.

Iterative Updates: Use the feedback to make iterative improvements to the prototype. This process helps in aligning the final product more closely with user expectations and requirements.

Final Validation: Once the prototype evolves to a stage where it meets the acceptance criteria, conduct a final round of Acceptance Testing to confirm that all requirements have been satisfactorily met.

Implement Prototyping in Acceptance Testing

The Role of Regression Testing

​

Regression Testing: Ensuring Consistency

Conducted after changes (like new modules or functionalities) are made to the software, to ensure that these changes have not adversely affected existing functionalities.

Beta Testing in Real-World Scenarios

​

Beta Testing: Final Validation

Beta testing is conducted by releasing the system to a limited audience outside of the company

Version numbering across different types of new information system testing

Version numbering across different types of new information system testing