4,575 reputation
1434
bio website linkedin.com/in/ethelevans
location Seattle, WA
age 30
visits member for 3 years, 7 months
seen Apr 9 at 23:35

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".


Mar
7
comment Is ageism in software development based on anything other than bias?
@T, I'd say you were the front of the wave of technology workers. I was referring to the wave of non-techie end users who are comfortable with technology, and they came much later.
Feb
2
awarded  Nice Answer
Dec
2
awarded  Popular Question
Dec
1
awarded  Yearling
Oct
20
awarded  Nice Answer
Oct
19
comment How to decrease errors before testing?
@P. Brian, wanted to add that, actually, it sounds like the test team is doing pretty well . . . the problem isn't that it takes forever to find the bugs, it's that "the number of errors is to damn high" and "we get an interminable list of things that we have to repair". That's not a test problem - that's a code quality problem that is upstream of test. There might also be test problems that are resulting in slow turn-around, etc., but they weren't mentioned (although some of my suggestions were targeted at that scenario).
Oct
19
comment How to decrease errors before testing?
@Bernard, Alan Page from Microsoft (author of "How We Test Software at Microsoft", which makes most "Top 5 Software QA Books" lists) wrote this paper on test code reviews: angryweasel.com/Articles/…
Oct
19
comment How to decrease errors before testing?
@P. Brian Mackey, I wasn't trying to say the OP should do all of these. I'm saying these are all things that can help. The OP can pick options that will work for their group and level of influence. OP sounds like s/he is looking for ideas to bring to a brainstorming session, and not just one fix.
Oct
19
answered How to decrease errors before testing?
Oct
11
comment Any recommendations for setup/teardown of browser automation testing?
+1, but wanted to add - look up Page Objects while you are at it! I've saved a ton of maintenance time by writing page objects to use in automated tests.
Sep
14
awarded  Nice Answer
Sep
14
comment Why is the dollar sign used to abbreviate the description of a cache?
I had no idea that was why . . . Allow me to make that facepalm a double.
Sep
14
comment What are the benefits of using comments
I would also suggest a good wiki with English documentation, outside of the code, as a good alternative - usable by more than just devs, e.g., PM and black-box testers.
Sep
14
comment What is O in Big O?
Thanks, Jonathan, I didn't know about that restriction. Small edit made, and thank you for thinking about that :)
Sep
14
revised What is O in Big O?
deleted 2 characters in body
Sep
14
comment What is O in Big O?
@Jonathan, I'm not sure exactly what minor change you want. Can you just go ahead and make the edit you want? Or, we could just let back2dos' answer stand, it looks like he might have ended up with the best answer anyway due to some excellent research :)
Sep
13
answered What is O in Big O?
Sep
9
comment How do you determine a 'release' date when a team uses Scrum
+1 Velocity is, IMO, the key concept to answering this question. The milestones idea is a good one for if upper management just can't wait until a realistic velocity can be established.
Sep
9
comment How do you determine a 'release' date when a team uses Scrum
I think this comment demonstrates one of the issues with using Scrum if the larger organization doesn't also use Scrum: You then have to create estimates about how many sprints you will need to eat through your current backlog and any items that will be added in the future, or you likely won't mesh with the larger organization's desire for longer-term timelines. It can be done (and, IMO, is often worth doing), but it is a real problem that needs to be resolved.
Sep
7
comment Application / Code reviews for lone programmers?
The "explain your design to a ten year-old" technique is just a variation on "rubber duck debugging". And yes, it works. I get my husband to help - he did tech support before becoming a SAHD so he understands things like servers, networks, etc., but is clueless enough about coding that I really have to break out what I'm doing at a very basic level to explain it to him. en.wikipedia.org/wiki/Rubber_duck_debugging