{"action":"created","issue":{"url":"https://api.github.com/repos/EaseTech/easytest-core/issues/113","labels_url":"https://api.github.com/repos/EaseTech/easytest-core/issues/113/labels{/name}","comments_url":"https://api.github.com/repos/EaseTech/easytest-core/issues/113/comments","events_url":"https://api.github.com/repos/EaseTech/easytest-core/issues/113/events","html_url":"https://github.com/EaseTech/easytest-core/issues/113","id":62422116,"number":113,"title":"Runtime configurable FilePaths","user":{"login":"Milton-Xiong","id":6244286,"avatar_url":"https://avatars.githubusercontent.com/u/6244286?v=3","gravatar_id":"","url":"https://api.github.com/users/Milton-Xiong","html_url":"https://github.com/Milton-Xiong","followers_url":"https://api.github.com/users/Milton-Xiong/followers","following_url":"https://api.github.com/users/Milton-Xiong/following{/other_user}","gists_url":"https://api.github.com/users/Milton-Xiong/gists{/gist_id}","starred_url":"https://api.github.com/users/Milton-Xiong/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Milton-Xiong/subscriptions","organizations_url":"https://api.github.com/users/Milton-Xiong/orgs","repos_url":"https://api.github.com/users/Milton-Xiong/repos","events_url":"https://api.github.com/users/Milton-Xiong/events{/privacy}","received_events_url":"https://api.github.com/users/Milton-Xiong/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2015-03-17T15:08:08Z","updated_at":"2015-03-26T15:04:41Z","closed_at":null,"body":"Dataloader FilePaths is configurable at design time by annotation, but only accepting constant. As a data driven test designer, I'd like to be able to re-config dataloader filepaths during runtime - provide APIs to update or modify FilePaths."},"comment":{"url":"https://api.github.com/repos/EaseTech/easytest-core/issues/comments/86558547","html_url":"https://github.com/EaseTech/easytest-core/issues/113#issuecomment-86558547","issue_url":"https://api.github.com/repos/EaseTech/easytest-core/issues/113","id":86558547,"user":{"login":"Milton-Xiong","id":6244286,"avatar_url":"https://avatars.githubusercontent.com/u/6244286?v=3","gravatar_id":"","url":"https://api.github.com/users/Milton-Xiong","html_url":"https://github.com/Milton-Xiong","followers_url":"https://api.github.com/users/Milton-Xiong/followers","following_url":"https://api.github.com/users/Milton-Xiong/following{/other_user}","gists_url":"https://api.github.com/users/Milton-Xiong/gists{/gist_id}","starred_url":"https://api.github.com/users/Milton-Xiong/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Milton-Xiong/subscriptions","organizations_url":"https://api.github.com/users/Milton-Xiong/orgs","repos_url":"https://api.github.com/users/Milton-Xiong/repos","events_url":"https://api.github.com/users/Milton-Xiong/events{/privacy}","received_events_url":"https://api.github.com/users/Milton-Xiong/received_events","type":"User","site_admin":false},"created_at":"2015-03-26T15:04:41Z","updated_at":"2015-03-26T15:04:41Z","body":"Hi Anuj,\nPerfect! your representation is very clear, that's exactly what I want.To be frank, I also don't like the coupling between tests and test data. But we have some very long long system test cases, or user acceptance tests, which perform some kind of \"end-to-end\" job sequences which from account creation, account checking, ... all the way to the account closing. Do I have a better choice?\nThanks,Sheng \n\n\n     On Thursday, March 26, 2015 6:59 PM, Anuj Kumar <notifications@github.com> wrote:\n   \n\n Hi Sheng,\n You can do it, but personally I would not advise you to do it, simply because of the coupling of test data with test class as well as the need to define a constructor. I am sure you are aware of the drawbacks of using Parameterized runner, specifically in scenarios where there can be multiple tests part of the same test class, that expects different input test data. You can have a look at my blog post on Parameterized runner for more indepth details on Parameterized runner : http://www.kumaranuj.com/2012/08/junits-parameterized-runner-and-data.htmlKeeping it aside, what I would like to say is that I think your use case is a good use case and it would be good if I can implement it in EasyTest code base, But I have to be clear on the requirements. A simple explanation from you would suffice to clear the requirements. This is what I have gathered so far from the discussion. Also is it possible to use gist for code examples. They make the readability of the comment a lot easier. \nI am trying again to visualize your above example as requirements:1) Let's assume we have two methods in our test class : M1 and M2. Lets also assume that M2 should run after M1. Also, lets assume that the test data for M1 is loaded in the memory and it has three rows of test data. This means that M1 will run 3 times.\n2) Then for each execution of M1, you would like to do the following:\n a) Load the test data for M2 based on the outcome of M1.\n b) Run test M2 using the loaded test data. Which means, if the test data loaded for M2 contains 10 rows, then M2 will run 10 times.Thus if the test data file for M1 has 3 rows and each of different M2 test data files have 10 rows, then the total number of tests executed will be : \n1 X 10 + 1 X 10 + 1 X 10 = 30 If the three test data files for M2 are different and each contains 5, 6, 7 test data rows respectively, then the total number of tests executed will be : \n1 X 5 + 1 X 6 + 1 X 7 = 18Do you think its a clear representation of your above example? \nDo you think if EasyTest provides such a functionality then you will use the functionality.Thanks,\nAnuj Kumar—\nReply to this email directly or view it on GitHub.   \n\n  "}}