World of bugs: let's find together

Bugs are so interesting and different! Let's try to find them & analyse

Transcript

1. World of bugs: let’s find together Alyona Tudan, QA Engineer, N-iX
2. About me • ~ 7 years in QA • Leading teams from 2 to 8 people • Mobile, desktop, WEB, BI, WS testing • Automation back-end tests writing & maintaining
4. Group: Documents • Ambiguous / inadequate / incorrect requirements • Missing requirements • Standards not followed • Errors in other documents: plans, designs, architecture
5. Back-end reqs: Front-end reqs:
7. Test case
8. Design Application
10. Conditions: Back-end implementation: is done first Functionality: to receive information for logged in and non logged in users Architectural solution: user has own additional account to secure flow Result: contact is not recognized without account
11. Group: UI • Typographical Errors • UI errors
15. Group: logical • Logic of code • Not logical functionality • Wrong user-journey
16. Condition: Query is necessary for status update during running automation tests Status should be updated from failed to released during procedure execution. There can be more then 1 entries with failed status Result: query is written
19. Condition: User see summary of entered before details during user flow Functionality: To check if information is right & continue. In case information is wrong user has to go back & edit details
20. Group: Technical • Variable Declaration Error • Standards, typographical Error • Data errors, errors of database
21. Condition: Automation framework to provide data driven testing using detailed reporting after regression run Functionality: Overload of details, script for deleting all the properties was used
22. Condition: To test data range of functionality
24. Condition: User see personal details entered before Functionality: To provide information already saved
25. Group: Localized • System errors • Browser error • Equipment errors
26. Condition: All empty spaces in red should be filled in with default details
29. Group: Mapping • Wrong connections between elements • Wrong relations between front-end & back-end
30. Condition: Send some money to your mom Functionality: To provide the money to other person using third party Result: Process fails
31. Condition: Send some money to your mom Functionality: To provide the money to other person using third party Result: Process fails Note: We need to check mapping with third party, like:
33. Group: combined • Logical? • Technical? • UI?
34. Condition: User changes own password Functionality: To change the password user has to fill in current password, new password & confirmation password To do: To fill in new password & confirm To fill in short current password • Logical? • Documents (requirements)? • UI?
35. Summary • Bugs can appear everywhere • We can’t get off the bugs without knowledge of the reason of their presence • The reason of bug’s presence can be hidden and not clear • Bugs can be cute & interesting 
36. Exhaustive testing is impossible • Questions • Comments • Wishes