Menu

1 / 2

Beyond Unit Tests: Implementing BDD and Penetration Testing in GBIM

DEV Community·Vincent Davis·6 months ago
#Q8F7eRE5
#critique#key#software#coding#testing
Reading 0:00
15s threshold

Claim Summary

This claim demonstrates that the GBM project has implemented advanced testing across four key areas:

Area Tool/Approach Primary Evidence

Security Testing GitLab SAST, Dependency Scanning, Secret Detection, OWASP ZAP baseline Successful FE security pipeline; availability of BE secret detection, BDD abuse paths, and ZAP baseline jobs.

Penetration Testing Abuse-case testing based on OWASP Top 10 8 abuse path scenarios covering login, registration, activation tokens, and admin submissions.

BDD Behave Django and Playwright BDD BE: 3 features, 12 scenarios, 57 steps passed. FE: 3 Playwright BDD tests discovered with a successful pipeline.

Stress Testing Locust Scenarios for registration bursts, authenticated activities, QA, and admin dashboards prepared as manual headless runs with HTML/CSV output.

The strongest claims lie in BDD, penetration testing, and the frontend security pipeline, all of which show "green" execution outputs.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.