Functionality Testing/Field Level Testing/Component
Testing
Testing each and every component thoroughly against requirement
specification is called as functionality testing.
• Component: text field, text area, dropdown, radio button, button, check
box, like, scroll bar, major tab, minor tab, grid, widgets, icon.
• Thoroughly means entering all possible inputs/ scenarios/cases.
Positive Testing- Testing by entering valid/expected data is called as Positive
Testing.
Negative Testing- Testing by entering invalid / unexpected data is called as
Negative Testing.
Why every req should be numbered?
• There will be clarity in the requirement.
• It will be easy to understand.
• Requirement becomes measurable and trackable.
• Communication b/w customer, developer and testing team become
smooth.
Functionality testing can be done in 3ways:
• Over testing
• Under testing
• Optimized testing
Over testing/Exhaustive Testing/Donkey Testing: -
Testing the features with same scenarios in different ways and scenarios which
doesn’t make any sense called over testing.
• If we do this type of testing then it is a time waste.
• Ex: 100rs, Rs 100, 100+100, 50+70, sin100 etc.
Under testing: -
Testing the feature with insufficient set of scenarios is called as under testing.
• If we do this, we will miss lot of scenarios and also defects
• Ex: 100, -100, 100rs, 0 etc.
Optimized testing: -
Testing the feature with those scenarios which makes sense is called as
optimized testing.
Here we are going to catch bugs with optimized time.
There are 2types: -
• Positive F.T- Testing each and every component by entering
valid/expected data is called as Positive F.T.
• Negative F.T- Testing each and every component by entering
invalid/unexpected data is called as negative F.T.
Note:
• Always we should start testing the application with valid data.
• If the field is working for valid THEN ONLY TEST application for invalid
data.
• If the feature is not working for one of the invalid data we can still
continue testing for some more invalid data.
• TE should not assume or propose the requirement.
• If you have any query then interact with developers, PM, customer and
get it clarified.
How to write functionality test scenarios?
Application Name: Facebook (Signup Page)
Component Name: First Name
(Format to write FT scenarios: To check that/To verify that/To test that)
1) To check that First Name text field should accept only alphabets.
2) To check that First Name text field should accept only 4-9 alphabets.
3) To verify that First Name text field should not accept space.
4) To verify that First Name text field should not accept Numbers.
5) To test that First Name text field should accept upper & lower case of
alphabets.
6) To test that First Name text field should accept special character.
Current city dropdown
1. To check that current city dropdown should accept all the cities which is
there in dropdown.
2. To check that current city dropdown user enters the city which is not
there in the list it should accept and it should display.
3. To check that user should be able to scroll the cities in the dropdown by
using scroll bar.
4. To check that current city dropdown when user points cursor on the city
it should get highlighted.