|
Not really, it was fine - though "J" for "Joined" could use a little improvement: "Short join with the third noble. Wait, I don't understand. (6)" might have worked better.
Good clue, keep it up!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Thanks, I see what you mean.
|
|
|
|
|
I don't get the wait part
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's irrelevant - probably should have been removed. "Wait, I don't understand" or "I don't understand" for jargon? I wouldn't use either, but it obviously worked!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
GKP1992 wrote: Was it too easy?
I didn't get it, so I did not consider it easy, if that helps! It probably doesn't help a lot as I get very few of them; yesterday's was the first for a long time.
As others have said, what is easy for one person is hard for others and vice versa.
|
|
|
|
|
Origa - Inner Universe[^]
A song recommended to me by YouTube.
I didn't know it yet, but apparently it's from the soundtrack of the Ghost in the Shell series.
It's pretty cool with fast paced beats and classical singing.
I still remember King of my Castle from the animated film.
If all Ghost in the Shell music is like this it seems I'll have to find the complete soundtrack
|
|
|
|
|
...Mothers[^]
Sorry, I couldn't resist (and I couldn't think of a way to make it work as a TotD if I'm honest) - I'll get my coat.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ugh, parents who show me pictures of their kids are the worst.
Especially if those kids are still ugly little trolls babies.
I do the same with my cat, but everyone loves cats
|
|
|
|
|
They all look like a cross between Winston Churchill and a shaved chimpanzee to me ... and I have to pick a feature and saye "(S)He's got your ... !" trying not to spot anything too out of proportion.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: (S)He It's impossible to get even that right
OriginalGriff wrote: a cross between Winston Churchill and a shaved chimpanzee Spot on!
|
|
|
|
|
Oh my, (s)he looks just like a...baby.
|
|
|
|
|
I know that "Did you keep the receipt?" doesn't go down well.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: I have to pick a feature and saye "(S)He's got your ... !" trying not to spot anything too out of proportion. That's like the "nice shoes" thing -- it's advisable to say it to women, even if you haven't looked at them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Sander Rossel wrote: I do the same with my cat
Show us, show us!
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
|
Cute!
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
So you like them when they show pictures of their holidays, don't you?
|
|
|
|
|
If they're nice pictures that give me an impression of their destination, then yes
|
|
|
|
|
Sander Rossel wrote: everyone loves cats
boooooo!
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
We had a period at work when one after the other became a mom or dad, and brought piles of their kids.
Then in spring one of the unmarried young guys bought himself a bright red motorbike (I believe it was a 1200cc), and spent the summer touring all of Norway on it, taking hundreds of pictures. When he returned, he had piles of photos of his bright red MC by the mountain lake, by the shore, at the ferry, at the mountain pass ... And it looked as if he always dusted off his MC before taking a picture.
He never told if this was a deliberate protest against those baby photos. I guess it was.
|
|
|
|
|
This is a reasonable setup, right?
1. Test Spec :
a.Explains the scope.
b.Defines how the testing should be approached.
c.It covers all the environment aspects : How to set up & start the tests.
d.Pointers to all the resources & links.
e.A link to test cases template
2. Test cases template Doc:
a.Testing team takes care of filling up this template.
b.Referring the Requirement doc & all the resources given to them for grasping the product.
c.They generate the whole test cases.
There are some confusion in team asking why we need two docs?
Does combining these two would make sense?
|
|
|
|
|
Where I work the developers work off 'user stories' and the testers write their tests independently, which I think is slightly ridiculous as it means that the testers get two days to test and discover defects then the devs have a short amount of time to put in the fixes and get it back to the testers.
The test documentation should really be part of the specification because the developers should ensure that their code passes the tests.
Sure it's good for the testers to independently try and break the code but for goodness sake why would you put the devs and testers in a position where they are not agreeing on what the functional specification is?
Actually I do know why, the answer is one word "Agile"
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 18-Jan-19 5:27am.
|
|
|
|
|
There are no rules; you can call your documents by any name you want.
However, if I were handed two documents with the names you've given, I'd assume that:- The Test Spec doc is the overarching description of how all tests of everything should be configured/followed/whatever, and should be provided be the chief tester.
- The Test cases doc contains use cases that have to be given attention when designing tests for a specific project/component/app/whatever, and should be provided by either the docs team or someone in a customer-facing role.
I wouldn't expect docs with either of those names to contain any actual tests.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|