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

Can't open a test case using multibyte path from JSON test suite at Windows #257

Open
teyamagu opened this issue Apr 29, 2015 · 1 comment
Labels
Milestone

Comments

@teyamagu
Copy link

situation

  • Windows 7
  • Firefox v35.0.1-
  • Selenium Builder v2.3.0-
  • JSON test suite: UTF-8
  • timing: Open JSON test suite
  • sample test suite is below ("スクリプト, "テストケース" is japanese)
{
  "type": "suite",
  "seleniumVersion": "2",
  "formatVersion": 1,
  "scripts": [
    {
      "where": "local",
      "path": "C:¥¥script¥¥スクリプト¥¥テストケース.json"
    }
  ],
  "shareState": false
}
  • JSON test case ("テストケース.json") has no problem when test case open only.

error

  • display error dialog
  • error message
ファイルを読み込めません。[Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFileInputStream.init]" nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)" location: "JS frame :: chrome://seleniumbuilder/content/html/js/selenium-ide/file-utils.js :: SeFileUtils.openFileInputStream :: line 48" data: no]

errordialog

cause (Maybe)

I think this error cause by 2 reasons.

at builder.io.addStorageSystem() in seleniumbuilder/chrome/content/html/js/builder/io.js

    1. can't japanese characters at file.setRelativeDescriptor(baseFile.parent, path.path);
    • but alphabet characters are OK.
    • e.g input "C:¥¥script¥¥スクリプト¥¥テストケース.json" -> output "C:¥¥script¥¥"
    1. file.exists() is "true" at Windows when file is DIR at file.setRelativeDescriptor(baseFile.parent, path.path);
    • file.exists() is "false" at Mac when file is DIR
@Zarkonnen Zarkonnen added this to the Builder 2.4 milestone May 21, 2015
@Zarkonnen Zarkonnen added the bug label May 21, 2015
@Zarkonnen
Copy link

Thanks, I'll look into this. It's almost certainly some unicode horror. :D

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

No branches or pull requests

2 participants