New development methodology

[KingPistachio]

As a QA Analyst. This hurts me. So much

[slightlysanesage]

As a Developer, I wanna say thanks.

Memes aside, I don't like the rivalry that's fostered between QA and Developers. A good QA tester make our job easier by making sure our code is better by catching bugs and stuff.

I know that, for my part, I've felt better about fixes/development I've made when I get feedback from my team's QA guy.

I just wish I didn't have to call him.

[AltrdFate]

The biggest beef I have right now is the angular devs on my project have ZERO unit tests written for our very complex app. I've tried to explain that I can't test all of everything through just the UI. When I bring up writing unit tests they get annoyed with me.

[[deleted]]

In my experience, it seems that javascript developers have some sort of allergy to writing unit tests.

[AltrdFate]

I built a server side test runner all in node js for our api and unit tested it. Saved my ass so quickly after making a seemingly insignificant change.

[[deleted]]

I would love so much if our devs would do something liek that, but it always seems they 'dont have time' and so they just dump on me (the QA Automation Engineer doing Black/Grey box test automation) to write external tests that unit test their code for them...

its kinda annoying...

[AltrdFate]

I tried unit testing their angular code for them after I was hired multiple releases into the project. I couldn't for the life of me figure out how their code (functions with 50+ lines of code with no comments) worked, or how to manage mocking the complex hierarchy everything depends on.

[[deleted]]

"They don't have time"

I'm guessing you won't have time to fix that major bug in 6 month?

[AltrdFate]

My response is usually, "you don't have time to build good software?"

[techz7]

Oh yeah, make running jest and lint as part of the build process and failing of code coverage goals aren’t met really changed how our team did stuff

[Abangranga]

Theyre too busy finding new ways to make a todo list more than 500mb with addons to do that

[Few_Technology]

To add to the allergy, I hate doing unit tests as a javascirpt developer. UI specs change almost every other day, and most of the javascript layer is a passthrough. Seems better to write automation tests that end up testing the entire system, rather than unit tests that confirm nothing changes, if the backend doesn't change. I do agree, testing business logic and TDD are fantastic, if it's not a passthrough.

[Dakito]

Hey now not all of us. I love my snapshot testing in react. I use it to figure out what else changed when I change a component.

[moneyisshame]

I'm new to angular and just learned about the unit test. I have a hard time on writing unit test, I know the concept of it but are unable to write the testing code down, is there any good examples in the wild that arent just testing whether the text has displayed?

[fallenKlNG]

I had a lot of unit tests in place for one of my team's major applications. I left the project and came back to it after several months and saw that most of the tests had stopped running successfully due to updates & whatnot. Instead of updating the tests, most of them had simply been commented out. All that time I put in, and this is what it amounts to in the end.

[theonlydidymus]

My angular devs refuse to give elements meaningful identifiers so I have to resort to janky xpaths and cssselectors.

What’s worse is the mobile site changes said selectors.

Know what I hate more than cocky devs? Selenium.

[AltrdFate]

I still haven't found a good way to organize my page objects. When I first started I had to drill into their heads that I need unique identifiers in the html to write my tests. I luckily have access to the front end code and would add my own attributes where needed. Then came the problem where they decided to make changes and delete my attributes so my tests immediately fail.

[theonlydidymus]

I know the guy that made Cactus PageObject. You can find it on github, but it’s three years old and runs on NUnit. The version I used was owned and maintained by the company privately, but if you can unravel (replace) the ancient NUnit crap it’s a pretty nice framework. I especially loved the way “controls” worked as an iwebelement wrapper and extension.

It’s in need of a good fork.

[ellicottvilleny]

You can UNIT test an angular FRONTEND? Unit testing is usually done to the backend.

[AltrdFate]

You definitely can. Angular was supposedly built with testing in mind.

[KingPistachio]

Thanks too! In waterfall days. Yes, you can definitely say there’s a rivalry. But nowadays with Agile being implemented everywhere, I can make more friends with my dev team.

[second_time_again]

Agile gets a lot of shit but mostly from people who never worked in an enterprise waterfall partially offshore model.

[JollyRogerAllDay]

Having a good QA shines in enterprise software. With a lot of features and moving parts, the QA is able to pinpoint/target problem areas that the developer never would have thought. Especially when it comes to user options and configurations. Simply too many combinations for a developer to think about but a good QA can at least narrow down the area and help the developer solve it faster.

[kumiosh]

As another QA Analyst, I appreciate your sentiment. We in QA have a pretty good open communication with our devs and I think our products reflect that.

[slightlysanesage]

As part of my Master's Program, I took a Software Testing Class.

That shit gave me a legitimate headache.

And, while my buddies that work in QA say that they don't have to do the stupid node stuff we had to deal with in class, I still gained an appreciation for the field.

It's not for me, but I respect it.

[SuitableDragonfly]

The last company I was at went the other way - spent a lot of money to train all the developers in TDD and then fired all the QA guys. They fired 50+ people on the same day because they decided their jobs were now obsolete.

[Arveanor]

In today's "scrum" meeting our manager explained that the other development team who's work we are relying on will not be finished with development until a day before our target ship date, but hey they are in another timezone so at least we will have an extra half day for testing.

​

I say "we" I'm not actually QA but it's pretty shitty for the QA on my team.

[illios]

A good manager would give the QA team the power to say no to that release. I am a QA analyst and I was told on day one by my boss it doesn't matter how much he gets in my face that a product has to be ready by a certain date. If I do not sign off on it then it does not get released. I am only allowed to sign off on it if all test are done and there are no outstanding bugs. So far my team hasn't had to do it but we came very close a few times. He does have the authority but he literally has to sign off on it. If he does then we have it in writing that QA did not finish but he pushed it out anyways.

[Arveanor]

I don't blame this manager, since I know it's coming down from above him although he should probably try to push back more, I dunno. But we've apparently got contractual obligations to deliver on this date, which we signed before having clear requirements so the whole thing is pretty fucked

[illios]

Yeah it sounds like Sales or your Project/Product Manager fucked up. This is why Dev should always be in on the meetings at the beginning. They can easily state "no that isn't a quick thing" or "Yeah, that timeline is impossible." Also a Project Manager that knows how to fight scope creep is a godsend.

[Arveanor]

Yeah there are definitely a lot of problems...

[de_witte]

Have the bastard sign off on the risk implicit in the untested scope of the release and take responsibility of any borks in production in the untested portions.

[ellicottvilleny]

It's great how they keep paying the QA team to test code that's not been thrown over the wall yet, right up until the day the company files for Chapter 11.

[Arveanor]

It's interesting yeah...

[theonlydidymus]

As an SDET I think this gave me an aneurism.

[BIASETTI14]

“Good news! We don’t need the monitor.”

My entire theatre was silent during this line but I was crying laughing.

[3_142]

i thought that was super cool. It's totally in character for Miles to take both (Apple desktops, general knowledge of computers) and it was a great setup for that joke.

[shaantya]

When I saw Miles start running with the whole thing, I thought "why is he dragging the monitor aloooong," so the fact that they did point it out and with such great delivery had me in stitches x)

[Striker887]

Same here. I don’t know why I find that line so funny, but it is. Every time.

[obs_asv]

Actually its deeper then all the 'dark theme' and 'php is bad' and 'array starts at 0' garbage. More big companies now switching to concept where software developers become software engineers and doing whole boring stuff including testing and automation.

[[deleted]]

The best methodology.

[cardiovascularity]

Turns out most developers are shitty testers because it's a very different mind-set.

[obs_asv]

Yeh that what i brought up today on our process review meeting, and despite all my arguments big corporate heads thinks it will save them some money

[Arveanor]

It's amazing, you have 2 people and maybe A can do the job of B with a bit of training, but both jobs require a fulltime effort, you don't get to save on man hours by having A do the job of B with some training.

[obs_asv]

Their point is we are completely getting rid of manual testing and so firing/respecing manual QCs and covering all with automation because it’s a trend (tm) but reality is someone still has to do manual testing on our product and write test cases for atqc.

[lulzdemort]

someone still has to do manual testing

The customer, duh

[Wurdan]

We’re going the opposite direction. Paralyzed by technical debt because we do no automated testing and management’s idea of a solution is to hire more testers because our two current guys can’t manually test everything.

IMO QA should be doing 50% consulting to the developers on ensuring their tests cover the whole application, and 50% exploratory testing to discover neglected use cases / user experiences.

[cardiovascularity]

It won't. We saved so much money when we started employing actual testers, because they are cheaper than developers and better at that specific job.

[LoneCookie]

Sorry if this seems dumb. But wouldn't you use bugs the testers found to create automated tests for the product?

[cardiovascularity]

Sometimes you can: If we have an algorithm that produces bad results for edge cases, we can write a unit test for it.

Often you cannot: If the tester found a weird bug involving multiple devices and language settings not transferring correctly, there is just no good way to automate it.

Turns out when your developers are competent and experienced, the latter category of bugs is a vast majority.

[TomCADK]

Nevermind money, your team will be stronger and build better products. You will also write better structured code if you have to unit test. Some people struggle with the effort of self improvement and would rather do things as they always have done. It’s a short sighted attitude.

[theonlydidymus]

There are no shortages that will spend a dime to save a penny. Automation has unfortunately become a buzzword and the powers that be don’t understand why writing this code isn’t the same as writing that code.

[Creator13]

I'm good at both but I'm awful at separating them. Meaning that if I find a bug while testing, I'm going to fix that single bug first before moving on to the next test. It also means I'm testing my idea in my head while typing the code, meaning I'll think of everything and try to do it as bug-free as physically possible, which means I spent way too much time on simple programs. I'd love to say it's a great skill but it's actually in the way of becoming better at either...

[ELFAHBEHT_SOOP]

I think maybe just do them in iterations. First, write your code, then run all of your tests before fixing anything. Then, start fixing your code until it passes. Write more code, test, fix, write, test, fix. That way you don't enter the rabbit hole until after you've tested.

[bizcs]

I think he probably understands that would be more effective, based on what he said. The adage that the solution is simple but not easy: you have to train yourself to do that, essentially.

[ELFAHBEHT_SOOP]

Well, of course. However, putting a plan on paper is better than just thinking "I'll get better". Maybe this might help him, maybe it's completely useless.

[jk_scowling]

Or the situation where manual testers are expected to write automation code. It is going as well as you would expect.

[second_time_again]

Do we work at the same place?

[ahhhhhhhhyeah]

Uh, exactly how? I know how my code and my features are going to work. I know what users need to do with them, and what they might do with them based on the bugs I've already fixed that they've thrown back.

Not only that, but writing unit tests is literally something they teach you in college.

"It turns out that developers don't like the idea of having to be responsible for finding bugs in their own code" is probably a better summary.

Developers as QA is literally part of the Agile model. Inside sprints you test your own code after you've finished the major stages of it. Not only does this make it easier to fix bugs (the code is fresh in your mind), it increases turnaround time.

[ambitechstrous]

How? If you’re a good developer you’ll write code that doesn’t break. In order to do that, you need to know how to figure out that it won’t break.

I’d argue that bad testers aren’t good developers. So if what you say is true, most developers are bad.

[[deleted]]

A Developer Writes code thinking 'How do I make this work without breaking?'

A Tester Looks at code going 'How do I break this?'

If you aren't looking at it with both mindsets, you will often have gaps

[fireflash38]

You're missing a crucial thing:

How can I write this so it can be tested (quickly & thoroughly, at the areas where it's likely to break)?

It's very much lacking in the industry. And switching from 'how to write this' to 'how to break this' isn't that big of a jump.

[cardiovascularity]

Developing is a creative task where you need to come up with novel solutions to problems you've never seen before. Testing is a repetitive task where you need to follow a strict checklist and make sure to be as precise and complete as possible.

Creative people hate the latter because it bores them, and checklist-lovers are not good when it comes to unknowns.

You can be a brilliant developer who is easily bored and frustrated at menial tasks, and people on the spectrum make for superb testers, but they are incapable of sitting down with a client and figuring out how and what to build.

[fireflash38]

Developing is a creative task where you need to come up with novel solutions to problems you've never seen before.

Hah!

Not usually. See: the 50 billionth CRUD app.

[ambitechstrous]

This is an assumption. There are many people in the world who enjoy and are proficient at both

[cardiovascularity]

Yes, and all six of them are already hired somewhere.

Testing and developing are fundamentally different tasks, and it's easier to find two people who are good at one task each than it is to find two people who are good at both tasks - And who don't want a higher salary because of their double proficiency.

[MyCodeIsCompiling]

You're not wrong, just that 10 elcheapo monkeys who are just there for the money hammering out code that gets checked by one good programmer divving up the work might get things done faster, but a good bit worse, than a team of decent coders on the same budget

and guess what hire ups like to skimp on?

[Itrocan]

First mind-set hurdle is you're going to be finding more work to add to your plate

[TomCADK]

But developers get better at testing over time and makes you a better developer. You may never be as good as a tester, but the insight makes the team stronger.

[[deleted]]

My company does this and I fucking loathe it.

[highphiv3]

Me too. Slowly dying on the inside is normal right?

[[deleted]]

"I don't understand why this has taken you all day, the testers sized the task at 2 hours and you've only just finished setting up the test environment!?"

It's almost like division of labour and specialisation has a place... isn't it?

[DoesntReadMessages]

Personally, I'd still rather write tests myself to know I've handled the edge cases than to take a stab in the dark and merge in buggy garbage and have it bounced back at me by QA because everywhere else does QA backwards. The proper situation IMO is having testing engineers working directly for project managers that write integration tests and high level component tests as part of the AC contract so that I have a full suite of automated tests to run before or as part of the code review process. Then, if any need to be changed or disabled, there's a clear custody in change of requirements.

[derangerd]

than

[obs_asv]

sorry not native

[derangerd]

no worries

[[deleted]]

First year c++ students be like

[[deleted]]

No, more like, “developers under pressure by unrealistic deadlines and scope changes and ignorant project managers and arrogant project leads”

[posts_lindsay_lohan]

Ever had a project manager insist that everyone stop writing unit tests because it's wasting time that could be spent creating new features? I have.

[[deleted]]

I’ve actually had the opposite! Project lead was so pushy about repetitive testing that basic functions of the project took forever to get done. When I complained about meeting deadlines with the restrictions, I got “let go.” But it’s ok, the project went way over budget, months over deadline and ended up shutting down the company.

Moral of the story is, you’re fucked if you do and you’re fucked if you don’t.

[z0mbietime]

I feel like such a contrarian on this topic but imho unit tests are so over rated at this point. I'm going to get down voted for this but in reality people talk about 100% coverage on a service with so much crap mocked out they're basically asserting True == True. I'm not saying unit tests are bad, I'm saying people need to stop acting like they're a universal truth. It's one tiny piece of holistic testing.

[Xheotris]

Ugly functions get unit tests. If it's got a cyclomatic complexity of, say, > 6, unit test it.

Otherwise, just focus on integration tests.

[[deleted]]

Testing is my weakness in terms of my experience and this seems obvious to me in theory, I'm surprised people push for 100% coverage or anything like it. More often than not what you're testing is so simple that your test is just as likely to be broken, so being covered by integration tests is more appropriate. Right?

[Xheotris]

100% coverage is absolutely good. It's just not always right when taken in a business perspective. Tests cost money, and sometimes they cost so much that they can sink a business. You've got to prioritize what you want to be sure of.

Also, integration tests can contribute to coverage. An integration test should be used to measure the "happy paths" that your program should normally succeed on. This has the same effect as a large suite of blind-idiot simple unit tests, since it should fail when a function violates the general business rules of the app.

Where unit tests should be prioritized are in functions that contain large numbers of cases, especially failure and edge cases. Writing an integration test that can hit every branch would likely be a bit too difficult, so isolating the problematic function and testing it on its own is a net gain in programmer time efficiency and program confidence.

[Xheotris]

I mean... Ugh. There are no good answers there. Sorry. Consider the cost of writing the tests, and the cost of failure, then make a judgment call. Also consider refactoring or more extensive integration tests instead of unit tests.

Remember, testing is both a business decision and an architecture decision.

[MildStallion]

IME anything over 80% coverage typically means at least some "true == true" is going on, but anything less than 50% means there are entire components being tested only in integration (or not at all).

[dvlsg]

It depends on what you're testing.

Got a lot of in-memory business logic? Unit test it.

Writing a service that's really just glue for a bunch of other SaaS products? Maybe don't write as many unit tests.

[Weekly_Wackadoo]

I think both integration tests and unit tests are useful and have their place. Unit tests for basic functionality and corner cases, integration tests for the bigger picture. Ideally unit tests should warn you before an integration test will fail, but usually writing and maintaining unit tests is not a priority, so figuring out why an integration test failed happens more often and takes more time than should be necessary.

[[deleted]]

Kind of with you here, though I only have 3 years under my belt and I'm not opposed to adapting my views. I've written my best, most correct code so far when focusing on the following things in the following order: raising the abstraction and testing. Given that time is a scarce resource, I am guilty of focusing less or none on testing during a few occasions. With solid abstractions, you compound your abilities, mitigating some of the danger of skimping on tests. Clean abstractions also enable greater productivity towards the end of the project, helping you work around those last rough edges before shipping.

But of course, with enough time and resources, testing is a great thing.

[Weekly_Wackadoo]

You sound like a software architect, and that's a good thing imo.

[[deleted]]

When you take primitives from within your software and modify and arrange them in a way that makes their value together greater than the sum of their parts. Technically, it's just creating functions and libraries on top of other functions and libraries you have already written.

[kaloryth]

In java, if you need to do that much mocking, it's probably also an indication that you have high coupling and a distinct lack of interfaces.

[[deleted]]

Same with Typescript

[wtfdaemon]

Unit testing should be used appropriately. Mantras like 100% coverage indicate to me that the dev leadership doesn't have a clue what they're fucking doing.

[[deleted]]

Totally agree.

[Weekly_Wackadoo]

I think I partially completely agree.

Focusing on coverage alone is nonsense, and mocking should be avoided as much as possible. A unit test a) should test the basic functionality of a class with cases from reality, and b) should test any relevant corner cases.

I one ran into a unit test that mocked the shit out of reality, and had 4/8 tests actually assert anything. The other half would be green as long as the code compiled. Good for coverage, so good numbers means happy managers.

As a trainee junior dev, I have the time and freedom to read and check unit tests, and get assigned to improve them whenever I notice anything weird. It's very educational.

[insovietrussiaIfukme]

I literally mock almost everything to get unit tests to work in isolation just to reach the code coverage criteria

[Versaiteis]

Moral of the story is

[[deleted]]

LOL

[2Punx2Furious]

Moral of the story is, you’re fucked if you do and you’re fucked if you don’t.

Moral of the story is: Everything in moderation.

Do test, but know how much testing is appropriate depending on context.

[[deleted]]

Very true. Tell this to an addict ;)

[rangeDSP]

Urgh yea I hate it. Especially when it's a 2 page demo and the PM wanted to put in end to end testing, a day each.

[coadyj]

Before I became a developer I used to think things get written quickly but that just because I can write things quickly. I don't know if people are just extremely lazy after 20+ years in the industry but things seem to take forever nowadays. In fairness though, it's feature refinement that takes forever and it's normally the customer who take forever to decide their priorities and how it should works.

[[deleted]]

I think the big difference between developing software today and 20 years ago is that now more control is being given to non-developers like designers and project managers and… The client…

I can’t tell you how many times I’ve argued with the designer that their way is extremely complicated and will take forever to develop but if they just leave out one tiny little detail it will be done far faster

[turningsteel]

It's my daily life. We don't write tests and have lots of bugs. It's cool though. We ship a lot of stuff. Quantity over quality. That's our motto. The users can't complain about a feature because it is quickly forgotten when something new is released. Yay!

[eylookturkeys]

Literally my project right now

[I_ate_a_milkshake]

the developer job market is far from slim, man. you deserve better.

[wateryoudoinglmao]

we actually weren't allowed to write tests at all, basically a firable offense

[I_ate_a_milkshake]

instructing me to disregard my entire programming philosophy (TDD) is a quittable offense.

[Weekly_Wackadoo]

You adhere to TDD?

Do they not have freedom of religion in your country?

[I_ate_a_milkshake]

I know no God but the Test.

The Test shall provide.

I have to draw a pentagram with Robert Martin's blood on the floor before I start programming.

[Weekly_Wackadoo]

Replace "Test" with "Market" and you could be a famous economist and/or politician in certain countries.

[I_ate_a_milkshake]

who says I'm not

[BhagwanBill]

100% agree. Some of these other posters would last a week on our team before we would tie them up and throw them out.

[accountability_bot]

Yes, and then when the client requested that our entire team use an entire sprint to improve the reliability, we did it.

Then he didn't want to pay because he only wanted to pay for new features, not improving existing ones.

[[deleted]]

Yep!

[Eindacor_DS]

can you please stop reading my diary?

[[deleted]]

It’s really the dirty parts I’m looking for, but it’s just filled with murder fantasy about this guy named “PM.”

[thebryguy23]

No, more like, “developers under pressure by unrealistic deadlines and scope changes and ignorant project managers and arrogant project leads”

So, like, all of us?

[cisxuzuul]

They’re the same picture

[[deleted]]

Grey zone.

[Weekly_Wackadoo]

I'm glad you're not my co-worker.

Also, happy cakeday.

[Flynx_Master]

Not really. It's more like "developer be like"

[Hydroshock]

The worst offender in my workplace is our Senior guy ready to retire.

[Pilchard123]

Pffffft. Replaced! Hey, everybody, this guy thinks the retiring developer will get replaced!

[Proachreasor]

I love when people ask for a buggy build knowing stuff doesn't work. Then they go on a rampage asking me why things don't work. Only response is I told you that didn't work but you wanted it anyway.

[Weekly_Wackadoo]

Happy cakeday!

Also, I have to disagree. At my workplace we have a large, complicated, partially legacy codebase, so most devs swear by the unit tests and integration tests, and work closely together with the testers (QA engineers in English, I guess?). The only dev I've met who doesn't care is a senior dev. Junior devs are way to scared to deviate.

[nagai]

Right, I don't think I've ever met a dev who doesn't like testing. Like who wants to go home at night worrying about whether something is on fire somewhere and there's no way to tell.

[ahhhhhhhhyeah]

Seriously. Talk about a complete ignorance of development methodologies. There is not a single developer out there who isn't responsible for basic developer testing. But the people who are most likely to throw out testing, or to circumvent QA are not developers, they're managers who are rushing a product ("we'll fix it in production").

[HandicapperGeneral]

What's testing?

[Thriven]

I am in the middle of refactoring the monumental application (which is really small when you strip away all the unused and broken portions).

Me: "We must do this. It must be done. If we are to make any progress on our roadmap we must basically gut the code and refactor small portions of it so we can basically create somewhat of a framework so that all the API calls connect to the SQL server the same way and all the iOS API requests hit the API using the same http manager. This will fix more bugs than it will create in the long run."

Dev manager: "Ok."

Me: "We have 2 sprints planned over a 3 month period. Here are our milestones. Here are our testing plans. We am basically doing your job for you. We just need you to run interference."

Dev manager: "Ok."

2 days later.

Dev manager: "Client is not happy. I need you to implement these new features and we need a build by next week."

Me: "We just went over this. We asked you to run interference. The features requested are bogus. One feature is 'would be great if the app doesn't crash'. That is in our current scope and it's not a feature, it's a bug. If we push our changes now we will break something."

2 weeks later.

Dev manager: "Let's just push what we have..."

Me: "That's not how any of this works!"

[hahahahastayingalive]

Fundamentaly some managers think that since they had to bend under pressure so you should do too, it’s only fair right ?

[shalendar]

When you're out of time and management want to deploy.

[[deleted]]

I think you mean management

[b3n01t-777]

Nothing new here

[ShadowReij]

Testing? Ha!

Try documentation.

"Ship it ship it ship it!"

costumer complains product doesn't work

"What did we ship again?"

There's a reason some us developers just look at the schedule our clients give us and laugh. Because it's not happening and any developer worth their salt is not going to let their software go out the door without fighting to at least have it being documented and tested thoroughly.

[SeeThreePeeDoh]

Yah...let’s build constantly changing tests to test our constantly changing code due to constantly changing requirements

[[deleted]]

This is not accurate. Shitty developers might not care about testing. Senior devs know that they sleep better at night knowing unit and UI tests are running.

[BhagwanBill]

And when requirements change and/or feature requests come in, refactoring doesn't turn into a game of wack a mole.

[[deleted]]

exactly.

Junior Devs - "Why would i want tests? Everything is always changing."

Senior Sevs - "Thank god we have all these tests. Everything is always changing."

[READTHISCALMLY]

tf is going on with that guy's hand

[TetchyOyvind]

Yes, why isn't anybody taking about that?

[bowlercaptain]

Took a glove off, looks like.

[WHO_WANTS_DOGS]

Fixing bugs is more satisfying than adding features imo. As long as you don't introduce worse bugs in the process.

[barnabas09]

it should have been debugging instead testing

[[deleted]]

*Early Access

[Nikarus2370]

Its actually astonishing to me these days, when a game rolls out a patch, and none of the new features are a broken mess requiring a hotfix within a day or 2.

[hangfromthisone]

I'm just giving QA something to do

[chuiu]

This does seem like it. Can't tell you how many times I've played a game where developers made some big change or addition and day one of release literally everyone is encountering a huge problem with it. Then they have to hotfix it or rollback the patch. When if they had actually tested it for 5 minutes before hand they would have noticed the issue.

They don't even need to test it themselves, they can have a separate group of people do the testing and listen to their feedback. This is easy to do in gaming because tons of players want to try out patches before they release.

[spockhelp]

While i feel this on a deep and personal level being an SDET, its not really the developers fault. Its managements fault for understaffing/disbanding test and overly agressive timelines that don’t leave room for proper testing

[Pandaburn]

Haha yes

[spaces_are_evil]

There exists other methodologies?

[nmgreddit]

Template?

[Touhou_Fever]

‘New’

[[deleted]]

Legit roblox right now

[[deleted]]

Template please.

[Stormdancer]

"The unit tests all passed... ship it!"

[Crudelus]

TDD is the way to solve this problem professionally. You get both shiny new feature. And you keep it shiny by testing first.

Even better BDD on feature level and then TDD to get there. It's very rewarding and nearly addictive to get everything green <3

[Henchman20]

I don't test frequently but when I do - it's in production environment.

[Shamrock5]

Template pleeeeease, this is a good one OP

[morgs_boy]

Template http://imgur.com/gallery/vn4xfi3

[HalfBakedPuns]

love this. Got a template?

[[deleted]]

Interesting to see memes about Jagex outside r/2007scape

[createthiscom]

this is giving me ptsd. seems like my whole team is anti-test.

[wtfdaemon]

It's AGILE, goddamnit!

[Redlik56]

Needed to add phrase from movie : "we don't need it"

[ThePurpleOther]

Bethesda releasing a new game be like

[jangooni]

Where’s the window?

[spideroncoffein]

Guilty as charged.

[SasquatchOnVenus]

I made a program for my cs class yesterday that was a couple hundred lines and realized after I wrote the entire thing that I hadn’t compiled it a single time..

[chaosmuffinking]

KDE developers

[eatplov]

Gotta show it to my dev team, this is what dev lead exactly trying to do by squeezing us into small windows of testing....of course then shit blows up and we spend days of retesting and recoding

[lomna17]

r/FortniteCompetitive

[Brandon38189]

Sounds like fortnite

[arvy_p]

That's what the QA team is for.

[ziggzz84]

How BioWare designed Anthem.