MD Ismail Hosen

@Freeflow I understand that but sometimes we must need to use collection(MAC OS). In that case i wanted to keep this option open.

@Vogel612 sequence equal is for array i guess. Not for collection

@HackSlash Thank you. I thought AreEqual too. But that is returning inconclusive result. I think i need to wrap it up with other way. Another problem is that collection key is not accessible in this situation right now i have.

Here is the simple test method :

Hello everyone. I want t check if two collection have same content or not. Which assert method should i use? Assert.AreSame is failing the case(as maybe it just check the pointer of those two collection). Assert.AreEqual returning inconclusive result.

@MathieuGuindon Thank you for the response. I have tried to run that i think that it is better to call that property instead of this.PropertyName as property implementation may be have something more than just getting UDT member value. Another issue i have found when following that article is that internal was never set to any object and that obj was never used. I guess that set result.user=obj instead of internal.

Both will work maybe but shouldn't rubberduck extract interface add that this.?

I was trying to follow the Builder Walkthrough article and i have noticed that for interface get implementation and i was seeing the github example class code and why both are not same?

Another thing i have noticed that could be improved is that if i want to add new member of UDT then encapsulate does that and it add that member at the end of the UDT which is good but property comes at the very beginning which could be add at the end and it will contain the order. It's personal choice though.

@MathieuGuindon In renaming case i have also noticed that if i rename any member of UDT then property name is not renamed accordingly. It just rename this.NewName. Maybe it can be improved too.

This is the issue..It is adding one more this as of it own and i need to check the accurate one in there.

@BZngr Previous version is enlisting all of the property. I am checking the new version again.

With version 2.5.2.5899

@this yes. I also have some scenario where i need to use some member only within that class and i need to use it in multiple sub.

Yes. It was working in the previous version but now it is not working. I don't know why.

It is generating all the property for that UDT members.

Like this one is working

So i need to declare the variable under UDT and then if i use encapculate then it will generate all the property for me. and i can get all the property and then i delete those which is not necessary.

Actually i was using this encapculate field option to get all the property let and get method for each of the member of the UDT.

Private This as TunitPrice>> this is the field

Did someone notice this type of unusual things ? Or am i doing something wrong?

Hi, I don't know if it is bug or i am doing anything wrong but Encapculate field refactoring is not working for some cases. Like in the image it is not showing any property. I am using the latest version which was released four days ago. in previous version it was working.

Got it. It's suggesting to use SequenceEquals method.

Now it's saying inconclusive..Any idea why not true or something.? Except Rubberduck documentation about unit testing if you have any suggestion for me to read?

@Vogel612 Thank you so much..Issue is solved..

Is this is related to early and late binding? But it shows me intellisense.

Hello everyone. I am very new to this unit testing in vba and i have a problem to test one part of code..I was just trying to add some functionality in collection like dictionary(although i don't know if that will be useful and speed performance) and i have a method like .getKeys which returns 1 based array of all the key..So i was testing that and i got this compiler error..can anyone guide me please..I am new to this chatroom too..So if i break any rule please correct me.