The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
Long time ago, I said this phrase to an American mate appreciating him on a good work.
He didn't exactly get what I meant. He was asking me, if it was a negative remark.
Bad surprise to me. The whole language I use is completely like an "AI" learning model. lol
I just keep watching what phrase, words the native speakers use, on what context, and I re-use it similar, applicable contexts. I think I do apply them right 90%.
Okay this "Strikes again" as far as I could grasp, it definitely looked like positive gesture.
Our mate Brad Kelly has written it here.(I see it's not positive again)*
It does not have a positive or negative meaning per se, imho. It depends on the context, the person who is phrasing and the person who is the object of the remark.
For example, let's say you have a coworker who uses to be very clumsy; today he spilt his mug of coffee on your desk, and the report you prepared is now useless. You say "Strikes again" -> negative
Now let's say there is another coworker, a brilliant developper who often find smart ways to solve complex issues. Today he found a way to finally implement this complex functionality which will allow to satisfy the customer's needs without impacting project's deadline. "Strikes again" -> positive.
If you say that to a guy who you do not know very well, and who does not know you very well either, then it can be confusing, thus his question about your remark.
"I'm neither for nor against, on the contrary." John Middle
It is a pejorative phrase, as in 'rampant malaria strikes again', although why it should be so is silly really, it is just the way it is used. (And it seems to be the same both sides of the pond, so must have a fairly well ingrained meaning).
Couple of new words for you perhaps, 'pejorative', means negative, derogatory, and 'pond' for the North Atlantic.
A friend of mine, who is absolutely clueless about computer, asked me "what is this multithreading error I was talking about, about?"
And I came up with this brilliant analogy, even if I do say so myself, to explain it: "it's like when you have 3 different managers all asking you to do different conflicting top priority things. in the end nothing much might happen!"
Multithreading? Drive to work every morning and you can learn all about it. Traffic lights show you everything about locks, deadlocks, race conditions and the strange phenomenon that some threads keep misunderstanding some part of green or red.
I have lived with several Zen masters - all of them were cats.
My mom is watching a TV show, and a woman on it was going on about a two page speech she had written about the pain and suffering she had gone through making Jell-O (Yes. Jell-O). Her husband (I think) then interrupted her and told her to stop being so Jell-O-dramatic.
What corny jokes do you guys have?
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
Hello all. I'm kinda ranting with Microsoft and I wanted to ask CPian community about it, because I may be overreacting.
For a new project I'm using unit testing, with vanilla unit tests. Many of these tests include throwing exceptions, such as ArgumentNullException, etc. Then I use VS 2017 Live Coverage to track how many code blocks are being tested and how many remain untested. I think this is a really useful tool, but I'm having this issue: when you run a test method with ExpectedExceptionAttribute, the Live Coverage marks the closing brace as not covered. Weird. This adds a small percentage of non-covered code blocks. So, as the project grows in size, and so do the unit tests, the % of non-covered blocks increase. In my project, I get a 8% of non-covered blocks just because of this scenario!
I filed a bug report[^] with Microsoft, and they replied that this was by design and thus they won't fix it.
So, what do you think, am I overreacting? I don't see the usefulness of a test coverage tool that will nevr yield a 100% coverage score unless I stop throwing exceptions altogether. Thoughts?
On my behalf of understanding i think you overreact and misunderstood the purpose of Expected exceptions!
Your Test is expecting that an exception is thrown at some place because (probably test data is, input parameters are forcing this).
So you can only test until the exception is thrown, which results in non full coverage of the method, but the test is correct!
If you want to do it completely right you might test a method way more than 10 times. Then you get 100% coverage on that method and yeah, obviously are running fully through it multiple times
SO microsoft is completly right on this behaviour because you broke your method somewhere (Exception).
I for my self write minimum 1 happy path, 1 total failure, and for each input param one test, plus if there is more than one input param several more where 1 param is good the other bad and vice versa.
I learned this thinking at DWX on a Software Testing session and this guy was totally right. 16 Tests for one method? Wow, overload, but no, you find the bugs, kill them and your method is 100% unbreakable
You're unlikely to get 100% coverage on all methods from a single unit test, you generally need a unit test per path through your code, and probably more on top. As well as the test that tests null arguments and exceptions you need tests that exercise the "happy path" and all other paths until you get 100% coverage. That's just what unit testing is.
Last Visit: 31-Dec-99 19:00 Last Update: 23-Nov-17 23:58