And it's still the same "coming soon" status on most subjects.
We had planned to have our wedding performed on Götheborg, it was all planned. We got a tour of the ship and discussed catering and so on. Suddenly a few months prior to the wedding they ghosted us, until they finally…
Because it's nice to have all tests in a single view and a single language, both unit, integration and end to end. Also regardless of keeping it in a _single_ language or tool, one might prefer to write tests in a .net…
The C# version is lacking the using pattern. https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...
Yeah you got my example. But regarding your conclusion; my entire point is that it IS more useful than you might think. Disclaimer: I often use emacs e g regex-replace and other means of code generation as well, both a…
Excel. Seriously. For more things than you imagine Let's say you want to make a property assignment for some class; this.a=x.a this.b=x.b ... While you probably would want to do this some other way to start with, and…
So this behavior is reasonable? Rectangle r=getRectangle(); r.width=1; Assert(1, r.width); //passes r.height=2; Assert(1, r.width); //fails or passes depending on subclass
And it's still the same "coming soon" status on most subjects.
We had planned to have our wedding performed on Götheborg, it was all planned. We got a tour of the ship and discussed catering and so on. Suddenly a few months prior to the wedding they ghosted us, until they finally…
Because it's nice to have all tests in a single view and a single language, both unit, integration and end to end. Also regardless of keeping it in a _single_ language or tool, one might prefer to write tests in a .net…
The C# version is lacking the using pattern. https://docs.microsoft.com/en-us/dotnet/csharp/language-refe...
Yeah you got my example. But regarding your conclusion; my entire point is that it IS more useful than you might think. Disclaimer: I often use emacs e g regex-replace and other means of code generation as well, both a…
Excel. Seriously. For more things than you imagine Let's say you want to make a property assignment for some class; this.a=x.a this.b=x.b ... While you probably would want to do this some other way to start with, and…
So this behavior is reasonable? Rectangle r=getRectangle(); r.width=1; Assert(1, r.width); //passes r.height=2; Assert(1, r.width); //fails or passes depending on subclass