Yes, absolutely. Maintainers test their own packages, and then submit them to Updates Testing by creating a new entry in Bodhi, our updates-handling system.
From there, anyone using the updates-testing repository will get that update — usually the next day. While the update is in testing, anyone with a Fedora account can log into Bodhi and give +1 or -1 votes, and can also note if specific bugs are fixed. If the maintainer or a QA team member has written a test plan for the update, those will be options to check, too.
If you look at https://bodhi.fedoraproject.org/updat... , you can see an update to the Geeqie image viewer I made earlier this year, and notice the linked test case. I got three instances of feedback, two of which are just +1 with comments "works" and "no problems spotted", while the other also checked off the boxes showing that they verified that the update fixes the linked bug and that they went through the test case.
Maintainers can set their package to be "pushed" from updates-testing to the regular updates stream if the vote reaches a certain threshold, and this is set to +3 by default. (For critical packages, any -1 will stop the automatic push regardless of the total.) Or, maintainers can also opt to not use this automatic system, and may choose to push to stable manually after 14 days in testing. If, during this testing period, there's a problem, the package can be "un-pushed" from testing (and presumably then replaced with a fixed update).
It sounds like you had a bad experience. Sorry that happened. It's pretty rare that a maintainer pushes a totally broken package, but it's possible — remember, the vast bulk of Fedora is maintained by volunteers, and sometimes things happen. (If you need a distribution where each package is checked by paid engineers, there's always RHEL!)
There are a number of things you can do to help. Of course, you could join the QA team. Or, you can enable Updates Testing on at least one of your systems, and provide feedback on updates as they come in. Or, you could just subscribe to the RSS feed for a package you care about (like this one for geeqie) and test updates as they come in.
As a project, we're working on increasing automated testing of updates. We should have a new system in place literally any day now where packagers can add tests which are run automatically on every build.
Another way to help is to help write those test plans I mentioned earlier. You don't need to be a packager or even a member of the QA team. Just follow the process to create the right pages in the wiki, and they'll automatically be linked in future Bodhi updates.
What did you find wasnt working for you? I found vlc crashing upon startup. Just curious what else is broken?? Terminal, gcc, emacs seem to good so far. As well as Chrome and video in chrome.
I also noticed something weird for the screen lock. The cursor was frozen and wouldnt move. I had to hard shutdown. But not sure if that is a persistent problem. Have to try to repeat