WEB APPLICATION

TESTING
SOCIALIST MODERNISM
Final Project
• Socialist Modernism
• Web Application
• Information Site
• Developed by BACU-to protect,monitoring,research for the current state of
those cities,including buildings,monuments,parks,squares,etc.
 TESTING APPROACH
• Ad-Hoc testing to decide if the application is worth further testing
• Exploratory testing for main functionalities
• Document the exploratory testing and write down the defects so they
can be replicated
• Focus where bugs were identified,more testing for that area
• Write smoke tests and execute them
• Write the test report
• Compatibility testing,UI testing,Component testing
 TOOLS USED
• Mantis Bug Tracker – Bug reporting
• TestLink – Test Case Management
• Snipping tool – Screenshoots capture
• Xmind tool – Mind maps
 TESTING TYPES
 Functional testing
 Exploratory testing
 Negative testing
 Positive testing
 Smoke testing
 Compatibility testing
 UI testing
 Usability testing
 Security testing
 BUGS OVERVIEW
4 Bugs: Major 2 Bugs: Minor 5 Bugs: Normal

1
1 1
1 1

4
1 1

Search
Search
Logo Search Email Links
List
Donate
TEST CASES OVERVIEW

Total: 30 Test cases

 TEST CASES RESULTS
Functionality Total Pass Failed Blocked Not run Defects
Search 5 5 0 0 0
Donate 2 2 0 0 0
Social Links 6 5 1 0 0 0055302
Icons 2 2 0 0 0
Navbar 6 6 0 0 0
Map & List 1 1 0 0 0
Back 1 1 0 0 0
Contact 3 3 0 0 0
News 1 1 0 0 0
About 1 1 0 0 0
Main page 1 1 0 0 0
Scroll bar 1 1 0 0 0
Overall results 30 29 1 0 0
Percentage 100% 95% 5% 0.0% 0.0% 2%
 CONCLUSIONS
 30 Test cases were executed to test the happy flows: 29 passed and 1
failed
 11 bugs identified: 4 major,5 normal and 2 minor
 Most of the bugs were identified by performing exploratory testing and
UI testing
 Data type used during testing: Blank, Valid, Invalid, Big data
 Fixing at least the major severity bugs is recommended
 LESSONS LEARNED
 Finding a buggy app was the main
challenge  Exploratory testing facilitates learning of
 Lack of requirements functionalities
  Less Is more, simple steps are better to use
Keep the bug reporting and test cases steps
and results easy to follow for writing test cases or report bugs
  The visual state of the site is very
Using to much invalid data in production
important because it is the visiting card
 Due to the fact that only one functionality
had problems, increased attention was
needed for the UI testing part to find
defects

Challenges Lessons
THANK YOU