Please enable JavaScript.
Coggle requires JavaScript to display documents.
DOU - Coggle Diagram
DOU
Related to Changes
-
-
Sanity
▶️ When searching algorithm is changed
:check: Then it must works as expected and passed all tests(minor bugs included)
Smoke
▶️ When searching algorithm is changed
:check: Then it must works as it expected(not included minor bugs)
Level
-
Component/Unit
▶️ When user finds vacation with filters
:check: Then user receives according responce with vacations
Integration
▶️ When tester wants to check interaction between website and other socical network auth
:check: Then tester choose registration method via social network
System
▶️ When tester opens root page
:check: Then root page processing ob backend and send to frontend (open in the browser)
Formal
Test based
▶️ When tester tests application functinonality
:check: Then tester checks all stages and functionality according to the checklist
-
Exploratory
▶️ When application reveices a huge amount of request
:check: Then the system automatically scale-up which give more opportunity
Code Access
White-box
▶️ When user click on profile image
:check: Then the request arrived to the corresponding root path and find other suitable mapping for proccesing request
Black-box
▶️ When user click on profile image
:check: Then it will redirect the user to another page with a couple of seconds interval
Gray-box
▶️ When tester click on the profile image
:check: Then it will redirect to another page according request
Types
Non-Functional
Usability
▶️ When user opens a site
:check: Then all necessary information must appear on the main page(navbar,logo)
Performance
-
Stress
▶️ When server can procces 5000 requests simultaneously during 2 second
:check: Then all request should be proccesed
Volume
▶️ When the user accounts amount grows
:check: Then the beackend must be able to work correctly and fine
-
-
Compatibility
▶️ When user opens the website on different devices
:check: Then all functionality and website appearance work fine
-
-
-
Run object
Static
Inspection
▶️ When some functionality has a problem with description/code
:check: Then a moderator creates a bug ticket for fixing it
-
Software analysis
▶️ When the structure of project sets by team lead
:check: Then all requirments and code structured by team lead
-
Expected Result
-
Negative
▶️ When user changes his profile information and leave requared fiields blank
:check: Then user receive error message
Execution
-
Automated
▶️ When tab "Вакансії" checks by tests
:check: Then software defines the correctness of the workflow algorithm