You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: