Suggestions

Open
#251 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
java

Research direction

The issue proposes several independent efforts: splitting HTMLReportGeneratorTest.java, reviewing dependencies, adding code review automation, cleaning files, adopting SonarCloud, and updating dependent repositories. Start by reading the repository contribution guidance and identifying which proposal maintainers want to pursue; the issue does not name tests or a single completion target, so clarify scope before estimating the work.

Written by the indexing model from the issue text.

Description

So Currently some files are Too Long to manage Like HTMLReportGeneratorTest.java and etc I suggest we open a new branch and work on Files to part the files in new files.

Addition of Lombok dependency I know that the framwork works on the no abstraction but i feel like more maintainable code is nessecary. Any other dependency like those.

Addition of Code Reviewers:- reviewers like code rabbit are free of oss repos that review a pr for atleast 2 changes this will reduce the workload for the Owner.

CleanUp Cycle:- I suggest we start a cleanup cycle for each file at a time remove the import from each file that are not needed and variables white spaces, Try to Improve performance in some parts by understanding data structures if any. This gives more new first issues and new contributors a chance to pick those up.

Sonar Cloud:- As the whole framework depends on java we can put this on sonar cloud for oss that's free for free code smell detection.

Update Cycles:- the dependant repos like migrator my have new issues as the framework has added new features improving that will be a good idea.

Dominant language
Java
Stars
12
Forks
6
Avg merge
10h
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seleniumboot/selenium-boot

All issues in seleniumboot/selenium-boot

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.