Equivalence Partitioning - Revision history

User at 15:34, 8 March 2024

2024-03-08T15:34:32Z

User at 00:54, 13 April 2023

2023-04-13T00:54:37Z

User: Created page with "'''Content Coming Soon'''"

2018-12-27T02:01:47Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

← Older revision		Revision as of 15:34, 8 March 2024
Line 8:		Line 8:

	Equivalence partitioning can be used in combination with other testing techniques, such as boundary value analysis, to provide a more comprehensive approach to testing. It is a widely used testing technique in software development, and is recommended by many testing standards and guidelines, such as IEEE 829 and ISO/IEC/IEEE 29119.		Equivalence partitioning can be used in combination with other testing techniques, such as boundary value analysis, to provide a more comprehensive approach to testing. It is a widely used testing technique in software development, and is recommended by many testing standards and guidelines, such as IEEE 829 and ISO/IEC/IEEE 29119.
		+
		+
		+
		+	== See Also ==
		+	*[[IT Strategy (Information Technology Strategy)]]
		+	*[[IT Governance]]
		+	*[[Enterprise Architecture]]
		+	*[[Chief Information Officer (CIO)]]
		+	*[[IT Sourcing (Information Technology Sourcing)]]
		+	*[[IT Operations (Information Technology Operations)]]
		+	*[[E-Strategy]]
		+
		+
		+
		+
		+
		+
		+	== References ==
		+	<references />

← Older revision		Revision as of 00:54, 13 April 2023
Line 1:		Line 1:
−	~~'''Content Coming Soon'''~~	+	Equivalence partitioning is a software testing technique used to divide input data into different sets or partitions based on their behavior or characteristics. The goal is to identify a representative set of inputs that can be used to test the system or software under different conditions, without having to test every possible input.
		+
		+	The key idea behind equivalence partitioning is to identify inputs that have similar behavior or characteristics, and then test them as a group. Inputs that are expected to produce the same output or behavior are grouped together, while inputs that are expected to produce different outputs or behaviors are separated into different groups.
		+
		+	For example, if a software system requires a numeric input, equivalence partitioning might divide the inputs into three groups: valid numbers, numbers that are too small, and numbers that are too large. Valid numbers would be tested to ensure that they produce the correct output, while numbers that are too small or too large would be tested to ensure that the system handles them correctly.
		+
		+	Equivalence partitioning is a useful testing technique because it can help reduce the number of test cases that need to be executed, while still providing a high level of test coverage. By identifying representative inputs that can be used to test multiple scenarios, equivalence partitioning can help reduce the time and resources required for testing.
		+
		+	Equivalence partitioning can be used in combination with other testing techniques, such as boundary value analysis, to provide a more comprehensive approach to testing. It is a widely used testing technique in software development, and is recommended by many testing standards and guidelines, such as IEEE 829 and ISO/IEC/IEEE 29119.