3,042 reputation
1630
bio website linkedin.com/in/ethelevans
location Seattle, WA
age 31
visits member for 3 years, 9 months
seen yesterday

SDET with 5 years of experience in software testing & BS in Computer Science. I'm also not very good at filling out "About Me" sections. I'm not as much of an expert as I'd like to be, so am trying to soak up knowledge as fast as I can while balancing work and "real life".


Jun
23
comment Where should test fixture code live?
Thanks, that's what I was looking for. I think I'm trending in that direction right now. The dev has some code snippets already available that I can borrow (I'm pretty lousy at Reflection). Can you edit your answer to include your comment? I'd like to have it be a bit more visible for anyone else looking at this question in the future :)
Jun
23
comment Where should test fixture code live?
Yeah, I strongly suspect that I will be maintaining fixtures partly to avoid this sort of dependency on the developers. So, it sounds like the fixtures in your system dynamically load the production code, but are all in their own solution? Thanks, this is helpful.
Jun
23
comment Where should test fixture code live?
And, thanks much for including your source code
Jun
23
comment Where should test fixture code live?
So far, what we are doing sounds similar - except it looks like all your tests can be executed without knowing anything about the SUT's actual code (e.g., by going through the browser). Am I right? What about testing a .dll that was going to be part of a larger system? Would you include every .dll you are testing in your test solution, or put your actual test code into the .dll solution? or would you create multiple solutions for collections of related .dlls that you are testing that include the .dll and your tests, and have your harness dynamically load their compiled code at runtime?
Jun
22
asked Where should test fixture code live?
Jun
21
answered Can exploratory testing replace executing manual functional tests?
Jun
21
answered What is the difference between regression testing and re-testing?
Jun
16
comment Should a test method test only one condition?
Good point about unit tests pointing to broken code more quickly if they just check one thing.
Jun
15
revised Should a test method test only one condition?
added 39 characters in body
Jun
15
revised Should a test method test only one condition?
added 322 characters in body; deleted 29 characters in body
Jun
15
answered Should a test method test only one condition?
Jun
11
comment Is it easier to write “correct” software in functional languages?
This is probably a better question for programmers.se
Jun
10
comment Workflow shortcut to meet the release deadline
We use a Q&A section on our functional specs on our team wiki to help spec out gray areas. As the whole team gathers information, they update the Q&A section of the wiki so we have the information in one place.
Jun
8
answered Test Strategy Documentation
Jun
7
answered Under what circumstances is Sikuli better for test automation than Selenium or Watir?
Jun
6
comment Writing automated tests for System.Web.HttpApplication
I'm not talking about Selenium or UI testing. "Record and Playback" with mocks means queuing values to return (recording), and then when your test calls those methods, they get returned (playback). Rhino Mocks is an example of this. See ayende.com/wiki/Rhino+Mocks+Introduction.ashx for examples of this style of mocking. Incidentally, while writing this comment I learned that Rhino Mocks has moved beyond Record and Playback to Arrange, Act, and Assert: blog.benhall.me.uk/2008/05/…
May
31
answered Who is ultimately responsible for issues that are found after software is released?
May
31
comment Should automated tests be efficient?
There was a joke on my old team that tests that don't do anything have the best performance. There was also a joke that when all the tests passed, there was something wrong with the test system.
May
31
answered Should automated tests be efficient?
May
27
comment Is a distinction between “testing” and “checking” useful?
Thanks, this is a great response. I like your point about guessing.