Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot prevent logs and other empty files creation #4144

Closed
PunkHaz4rd opened this issue Mar 9, 2017 · 2 comments
Closed

Cannot prevent logs and other empty files creation #4144

PunkHaz4rd opened this issue Mar 9, 2017 · 2 comments
Assignees

Comments

@PunkHaz4rd
Copy link

Bug report

There should be an option to just not create, or at least clean after itself from First Run, Local State & the folder Default created after a run.

  • Node Version: v7.2.1
  • Protractor Version: 5.1.1
  • Angular Version: 1.3.13
  • Browser(s): chrome
  • Operating System and Version linux
  • Your protractor configuration file:
exports.config = {
  baseUrl: 'http://localhost:8100',
  capabilities: {
    'browserName': 'chrome',
    'chromeOptions': {
      args: ['--disable-web-security', '--user-data-dir']
    }
  },
  directConnect: true,
  jasmineNodeOpts: {
    isVerbose: false,
  },
  specs: [
    'e2e-tests/**/*.test.js'
  ]
};
  • A relevant example test
    Just write any test at all.

  • Output from running the test
    whatever the output of the test, I always get First Run, Local State & the folder Default that polute my test folder.

  • Steps to reproduce the bug
    Just launch whatever test.

@NickTomlin
Copy link
Contributor

NickTomlin commented Mar 9, 2017

This is a result of --user-data-dir and not something that protractor itself is doing. I don't think this is our responsibility to clean up for a chrome driver option. My thoughts here are that should set this to a temporary directory (e.g. randomized) or a directory that you can clean up in a before/after block for your tests.

That said, i'm very open to discussion here.

@NickTomlin NickTomlin self-assigned this Mar 9, 2017
@PunkHaz4rd
Copy link
Author

PunkHaz4rd commented Mar 10, 2017

Oh ! That's why I couldn't find anything that linked those files to protractor in the first place. My bad.
I'll set up the cleaning myself, it would not make sense to code something that check if that option is used then clean up yourself while not having any means to know about the evolution of that feature / bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants