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

How we are planning to address Collection as parameter? #55

Open
ravi-polampelli opened this issue Oct 24, 2012 · 1 comment
Open

How we are planning to address Collection as parameter? #55

ravi-polampelli opened this issue Oct 24, 2012 · 1 comment

Comments

@ravi-polampelli
Copy link

I see there might be issue if collection has been sent as parameter,
if Collection is generic collection then it is hard to determine what type of data is there in Collection?
If Collection is tied to a data type or class, then it is bit OK to have that particular class fields as parameter. but still not sure how many objects we can populate in that collection,
How converter handle these scenarios?

@anujgandharv
Copy link
Member

Since the author of Test class will be responsible for writing Converters, he would already be knowing the type of collection he has to instantiate for the test.It might be tricky with generic Collections I agree and to be honest I havent given a thought to this. So for eg. if a test method takes as parameter : Collection then I dont think EasyTest can currently handle this scenario with grace. I think this is a very good point you have raised and we have to think about how we can handle this situation.

I will try to think over it in the next few days and will share whatever I have thought. You can also do the same.

Cheers!

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