Alex Melnikova discusses the benefits and drawbacks of using shared vs individual test environments and provides the results of her survey intended to gather the preferences and reasoning from QA professionals.
There is a lot of interest in organizations around a transformation to agility. However, the focus is usually on agile development, so it may not be clear how software testing is done in agile. If you're responsible for leading your testing teams, don't let them be left behind. Here’s how you can make testers part of the transformation, too—step by step, because this is agile, after all.
Testers and developers often have a strained relationship. Each side has a certain level of expectations as to what the other side should know and do, while there is little understanding of the constraints, conditions, and requirements that the other team has to work within. But it does not have to be this way. A little effort in giving more specific and helpful feedback can go a long way toward improving attitudes.
Whole-team testing means the whole team understands and participates in testing, using testing education as a tool to support quality efforts. And to be able to support testing in a meaningful way, team members must experience how testing is done by professional testers. Understanding skilled testing can help non-testers realize what quality criteria should be there and what elements of a product contribute to great quality.
Just because a software team adopts agility doesn’t mean they’ll see results. Being flexible has its benefits, but ensuring that the team is given total responsibility to make decisions may be more important.
Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
Gene Gotimer, principal consultant at Coveros, chats with TechWell community manager Owen Gotimer about the challenges individuals and organizations face while we work from home during this global pandemic and how getting thrown into remote work could shape our future.
Hans Buwalda, CTO at LogiGear, discusses how to accomplish same-sprint automation. The testers, automation engineers, and developers are all working in the same sprint, so you can immediately hand off what you are working on and get it into the next phase. Hans also talks about why it’s so challenging to get teams to agree on same-sprint automation, saying the commitment for the sprint needs to come from the team as well as the business.
Aprajita Mathur, bioinformatics software test manager at Guardant Health, discusses how to develop yourself and why it's so important to take the time to do so. She explains that your personal life will always be more significant than any work you need to get done, and she gives strategies for how to talk with your manager as well as your team when you are feeling overworked and need a break. Aprajita believes if you are self-aware and have open communication, then having these conversations will be easier and you can focus on yourself.
Chris Loder, an automation architect at InGenius Software, talks about his open source framework for automation, as well as why he says he left testing behind and started automating. He also discusses running the Test Lab at STARWEST, where conference attendees can practice their QA skills together to solve puzzles and test code. This year there were new AI features and an Automation Zone, where participants got hands-on experience with automation.
Drawing from her own experiences across twenty years in a range of industry roles, Jaimee Newberry shares true stories of at least a dozen tiny but important things she still sees every day that could make all the difference in how people work with you.
AWS Lambda is a serverless architecture that relieves you of hardware and scaling setup concerns. AWS Lambda functions are used by many organizations for serverless application development and automating DevOps tasks.
Most teams that do agile development start with Scrum. And why not? Scrum is a proven method for focusing your team, ensuring that work adds value, and minimizing the risk with release. Then, after awhile, Scrum becomes stagnant.
Teams can hesitate to adopt agile practices, even when there’s a clear desire for transformation at the executive level. But there are strategies for coaching agile-skeptical teams into an agile mindset.