Pramod Kumar Yadav comments

Results 7 comments of


                                            Pramod Kumar Yadav

Suggestion: new ChromeOptions().setHeadless(true); line from your tests is a mandatory requirement for tests to run. In absence of this, tests will fail for another project (like say mine). It could be a good idea to add it in readme.md file.

Hello Mark, It does. Maybe its also good to mention the error user will face if they fail to add this option. This way, if someone searches for an answer...

Suggestion: new ChromeOptions().setHeadless(true); line from your tests is a mandatory requirement for tests to run. In absence of this, tests will fail for another project (like say mine). It could be a good idea to add it in readme.md file.

Hello Mark, To add, in the demo -> run.sh, The commands for windows are a little different (differences are highlighted in bold): **$DOCKER_IMAGE**=markhobson/maven-chrome docker pull $DOCKER_IMAGE docker run --rm -it...

feature: would it be an idea to keep sessions under TestRuns? say TestRun1, TestRun2 etc.

Sounds good :)

feature: add gitattribute file to denote which files should be treated like text for line endings.

example: adding below to .gitattributes file will add line endings to below type of files automatically - something that editorconfig cannot do for conf or properties file. *.java text *.conf...

Bug: Version/Overwriting issues when pushing new secrets from local with already added/updated/deleted secrets in UI.

Another workaround to avoid this issue could be to only allow "npx dotenv-vault@latest pull" from local and do all "pushing" from UI - just a thought.

Updating threads in multiple channels doesn't work correctly

Hi @seratch , I wanted to use this feature to trigger e2e tests post new deployments and update team on a team channel and individuals using the bot. Since e2e...

Updating threads in multiple channels doesn't work correctly

Thanks for the suggestion @zimeg. In my use case, I am trying to send a message to the github _actor_ whose last commit (and merge to main) triggered the deployment....