I try to keep the music upbeat (stadium rock from the 80s is good for that) and similar enough that it is more of a consistent noise than anything.
My desk is near the foosball table and big conference room. So much noise.
The testing tag has some stuff, but perhaps I'll try to make some posts about it in the future. I only ever see resources on "yo, you should unit test" not, like, how to think about unit testing ideas or the various forms of QA automation testing out there.
I just learned on the job, but my interpretation is E2E (end-to-end) should be entirely full stack. As close to prod as you can reasonably get, it should cover all integrations outside of third party vendors (like, Paypal integration doesn't need to be turned on for real). Test the end product as if you're a drunk user. Do stuff right and wrong and make sure stuff handles that.
Hi, I came here, arriving to this post looking for anything else you would have written already about QA. Looking forward to a post similar to this comment but in detail or lengthy
Hi! It's been on my to-do list of doom for a while now, mainly because grad school kept putting it off and then work got hectic (but I graduated!). Tomorrow I go back to work after a little vacation, so maybe now things are finally reset enough for me to actually create content :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I try to keep the music upbeat (stadium rock from the 80s is good for that) and similar enough that it is more of a consistent noise than anything.
My desk is near the foosball table and big conference room. So much noise.
The testing tag has some stuff, but perhaps I'll try to make some posts about it in the future. I only ever see resources on "yo, you should unit test" not, like, how to think about unit testing ideas or the various forms of QA automation testing out there.
I just learned on the job, but my interpretation is E2E (end-to-end) should be entirely full stack. As close to prod as you can reasonably get, it should cover all integrations outside of third party vendors (like, Paypal integration doesn't need to be turned on for real). Test the end product as if you're a drunk user. Do stuff right and wrong and make sure stuff handles that.
Thanks for the pointers!
Hi, I came here, arriving to this post looking for anything else you would have written already about QA. Looking forward to a post similar to this comment but in detail or lengthy
Hi! It's been on my to-do list of doom for a while now, mainly because grad school kept putting it off and then work got hectic (but I graduated!). Tomorrow I go back to work after a little vacation, so maybe now things are finally reset enough for me to actually create content :D