{"action":"created","issue":{"url":"https://api.github.com/repos/galenframework/galen/issues/344","labels_url":"https://api.github.com/repos/galenframework/galen/issues/344/labels{/name}","comments_url":"https://api.github.com/repos/galenframework/galen/issues/344/comments","events_url":"https://api.github.com/repos/galenframework/galen/issues/344/events","html_url":"https://github.com/galenframework/galen/issues/344","id":117091277,"number":344,"title":"Relative path in TestSuites not resolved","user":{"login":"hypery2k","id":979121,"avatar_url":"https://avatars.githubusercontent.com/u/979121?v=3","gravatar_id":"","url":"https://api.github.com/users/hypery2k","html_url":"https://github.com/hypery2k","followers_url":"https://api.github.com/users/hypery2k/followers","following_url":"https://api.github.com/users/hypery2k/following{/other_user}","gists_url":"https://api.github.com/users/hypery2k/gists{/gist_id}","starred_url":"https://api.github.com/users/hypery2k/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hypery2k/subscriptions","organizations_url":"https://api.github.com/users/hypery2k/orgs","repos_url":"https://api.github.com/users/hypery2k/repos","events_url":"https://api.github.com/users/hypery2k/events{/privacy}","received_events_url":"https://api.github.com/users/hypery2k/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-16T10:18:31Z","updated_at":"2015-11-17T09:20:37Z","closed_at":null,"body":"If you're using test suite and the paths to the Spec files are relative the paths are not resolved, see the following folder structure:\r\n```\r\nproject-dir\r\n  test\r\n    layout\r\n      specs\r\n        home.spec\r\n      homepage.test\r\n```\r\n\r\nIf I run Galen from the project with `galen test homepage.test` dir I get the following error:\r\n```\r\ncheck specs/home.gspec --include \"mobile,phone,XS\"\r\njava.io.FileNotFoundException: specs/home.gspec\r\n\tat com.galenframework.speclang2.reader.pagespec.PageSpecReader.read(PageSpecReader.java:46)\r\n```\r\n\r\nhomepage.test:\r\n```\r\n@@ table browsers\r\n    | browerName | browser |\r\n    | Chrome     | chrome  |\r\n@@ table devices\r\n    | deviceName    | tags                      | size      |\r\n    | XS            | mobile,phone,XS           | 320x600   |\r\n    | S             | mobile,phone,S            | 500x800   |\r\n    | M             | mobile,tablet,M           | 780x1080  |\r\n    | L             | desktop,L                 | 1024x800  |\r\n    | XL            | desktop,XL                | 1280x1024 |\r\n\r\n@@ parameterized using browsers\r\n@@ parameterized using devices\r\n@@ groups homepage\r\nhomepage on ${deviceName} in ${browerName} browser\r\n  selenium ${browser} ${websiteUrl} ${size}\r\n    check specs/home.gspec --include \"${tags}\"\r\n```\r\n\r\nI think adding relative file read [here](https://github.com/galenframework/galen/blob/master/galen-core/src/main/java/com/galenframework/utils/GalenUtils.java#L363) with a '.' could solve this issue-"},"comment":{"url":"https://api.github.com/repos/galenframework/galen/issues/comments/157316681","html_url":"https://github.com/galenframework/galen/issues/344#issuecomment-157316681","issue_url":"https://api.github.com/repos/galenframework/galen/issues/344","id":157316681,"user":{"login":"ishubin","id":949577,"avatar_url":"https://avatars.githubusercontent.com/u/949577?v=3","gravatar_id":"","url":"https://api.github.com/users/ishubin","html_url":"https://github.com/ishubin","followers_url":"https://api.github.com/users/ishubin/followers","following_url":"https://api.github.com/users/ishubin/following{/other_user}","gists_url":"https://api.github.com/users/ishubin/gists{/gist_id}","starred_url":"https://api.github.com/users/ishubin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ishubin/subscriptions","organizations_url":"https://api.github.com/users/ishubin/orgs","repos_url":"https://api.github.com/users/ishubin/repos","events_url":"https://api.github.com/users/ishubin/events{/privacy}","received_events_url":"https://api.github.com/users/ishubin/received_events","type":"User","site_admin":false},"created_at":"2015-11-17T09:20:37Z","updated_at":"2015-11-17T09:20:37Z","body":"Not sure about that. While inside specs it does make sense to do that, and it is already implemented like that and works. But for test, I would say it is the same as in Java project you have tests located in various levels (packages) but they all refer to files starting from working directory. I think implementing this feature will make it more confusing.\r\nFor instance in other test projects Galen tests are spread in different folders and the specs are all managed in a separate folder. If every test would start searching for a spec within its own folder - that would make a mess there"}}