• Functional testing — are we building the product right?
• More about types of testing
• Detailed test cases

Functional testing — are we building the product right?

• Determine if a piece of software is acting in accordance with pre-determined requirements.
• Functional testing is validating if a system works as intended, meeting any given criteria.
• Most functional tests follow the Arrange-Act-Assert model:
1. Arrange, or set up, the conditions for the test
1. Input values
2. Act by calling some function or method
1. Execute test cases
3. Assert that some end condition is true
1. Compare actual result and expected
• The main points of functional testing
1. Understanding customer requirements
2. Testing input data
3. Gathering expected results
4. Executing test cases
5. Comparing actual vs. expected results
6. Updating results according to test case
• Functional testing best practices – focus on:
1. GUI coverage: with different screen resolutions, GUI elements like font size, color, etc.
2. Input domain coverage: taking valid and correct size with appropriate formats.
3. Return of correct data with correct input.
4. Order of functionality (i.e. Tab order).

More about types of testing

Detailed test cases