« first day (1821 days earlier)      last day (1359 days later) » 

Duga
Duga
12:01 AM
RELOAD!
[rubberduck-vba/Rubberduck] 2 opened issues. 9 issue comments.
[rubberduck-vba/RubberduckWeb] 4 commits. 976 additions. 752 deletions.
[Zomis/minesweeper-core] 7 commits. 229 additions. 150 deletions.
[Minesweeper] Games Played: 115, Bombs Used: 60, Moves Performed: 14150, New Users: 14
 
IvenBach
IvenBach
Enjoy the weekend pond. Get some fun coding done.
 
mansellan
mansellan
12:24 AM
off to barcelona on monday
 
Mathieu Guindon
Mathieu Guindon
12:34 AM
@mansellan nice! enjoy the trip!
 
Duga
Duga
1:27 AM
> I can see it going either way. At a more basic level I think Inconclusive is more appropriate because a pass/fail is conclusive. Anything else a nebulous mumble mumble at best. A descriptive message would help whoever is running the test to make the required changes, ultimately ending with a definitive pass/fail.
 
 
4 hours later…
this
this
5:10 AM
which resource do you recommend for teaching beginners git?
Looks like https://learngitbranching.js.org/ was recommended here before. I think that's the one I'm trying to remember.
 
Vogel612
Vogel612
5:27 AM
Somewhat very technical, but I learned a lot from it
Unrelatedly: my parents' dog woke me after mildly more than four hours of sleep... bleargh
 
 
2 hours later…
IvenBach
IvenBach
7:02 AM
@this That was helpful getting a visual understanding.
You teaching a co-worker?
 
 
2 hours later…
M.Doerner
M.Doerner
9:01 AM
I learned git reading through atlassian.com/git/tutorials
I think it does a quite good job explaining what a good workflow might look like.
 
Duga
Duga
> What @retailcoder said hits the core of the issue, though. The function does not return the expected type, not even the expected value. That's a clear test failure, making the test inconclusive for type mismatches is incorrect behaviour.

For what it's worth: `Assert.SequenceEquals(Empty, Empty)` could be argued to be supposed to pass, but currently result in an `Inconclusive` state.
 
 
6 hours later…
Duga
Duga
2:48 PM
> Thanks, Mathieu. That is what I suspected - the Function itself being Variant/Empty is the issue. When I said "is expected to fail" I was meaning that the test failure would report back that they sequences are not the same, not that the Assert itself would fail with its error message. What I should have done is actually return an array that would not cause the Assert object to fail, but the test to return not equal. A small difference, and really not an issue since the function does indeed fai
 
Duga
Duga
3:32 PM
> So here is what I did:
In the Function CollectionToArray:
Dim result As Variant
Redim result (0 to 0)
CollectionToArray=result

Now the SequenceEquals test fails nicely (grin) with this Message: "Sequence Assertion failed. expected has 2 dimensions; actual has 1 dimensions [sic]. Array Conversion Failed" which is a very nice failure - it not only includes my custom message (Array Conversion Failed) but as an added bonus tells me a lot about the specific failure.

Thanks so much for you
 

« first day (1821 days earlier)      last day (1359 days later) »