OWASP / OWASP/SecurityShepherd
Implement End-to-End Testing
Open
Nobody has claimed this yet.
Test Automation
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
As a contributor
I want to know if my changes have had a negative impact on the system and block a build / merge
because this will remove the need to manually test and ensure a stable release
Definition of Done
Utilise Selenium within the product
Ensure there is a test for core, module & mongo, so test;
- Login
- MySQL Lesson 1
- MongoDb Challenge
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or test entry points are named. Start by locating the project's test and build configuration, then map the core, module, and mongo areas named in the issue; done means Selenium coverage for login, MySQL Lesson 1, and the MongoDB Challenge can block a build or merge when they fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb, mysql
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100