“Quality Engineering” is the new darling of tech buzzwords, but what does it actually mean? Is it just a shiny rebrand of Quality Assurance, or does it bring something new to the table? In Rafael E. Santos' latest blog, Clearing the Fog Around the Quality Engineering Term, Rafael digs into the definitions, the confusion, and the hype. If you're trying to navigate the chaos of testing terminology and figure out whether you really need a "Quality Engineer," this post is for you. Here's a hint: At Testaify, we believe it's not about the?title?but having the?right people who deeply care about quality and know how to elevate your testing strategy. #qualityengineering #softwaredevelopment #qualityassurance https://lnkd.in/e_jiZNrf
Testaify, Inc.的动态
最相关的动态
-
This post is another attempt to explain Quality Engineering and why nothing is new here. Don't let buzzwords run your career.
“Quality Engineering” is the new darling of tech buzzwords, but what does it actually mean? Is it just a shiny rebrand of Quality Assurance, or does it bring something new to the table? In Rafael E. Santos' latest blog, Clearing the Fog Around the Quality Engineering Term, Rafael digs into the definitions, the confusion, and the hype. If you're trying to navigate the chaos of testing terminology and figure out whether you really need a "Quality Engineer," this post is for you. Here's a hint: At Testaify, we believe it's not about the?title?but having the?right people who deeply care about quality and know how to elevate your testing strategy. #qualityengineering #softwaredevelopment #qualityassurance https://lnkd.in/e_jiZNrf
要查看或添加评论,请登录
-
Do titles matter? Yes and no. A title is supposed to clarify someone's role and responsibilities. But what happens if a title is a buzzword? Quality Engineering is just that... Rafael E. Santos' new blog is worth a close read. https://lnkd.in/ecVugj6M
“Quality Engineering” is the new darling of tech buzzwords, but what does it actually mean? Is it just a shiny rebrand of Quality Assurance, or does it bring something new to the table? In Rafael E. Santos' latest blog, Clearing the Fog Around the Quality Engineering Term, Rafael digs into the definitions, the confusion, and the hype. If you're trying to navigate the chaos of testing terminology and figure out whether you really need a "Quality Engineer," this post is for you. Here's a hint: At Testaify, we believe it's not about the?title?but having the?right people who deeply care about quality and know how to elevate your testing strategy. #qualityengineering #softwaredevelopment #qualityassurance https://lnkd.in/e_jiZNrf
要查看或添加评论,请登录
-
Think in 3’s ?? When it comes to quality engineering at a organizational level, I gravitate towards explaining it in 3’s. Here's a breakdown: ?? 3 core pillars of quality engineering: - Quality assurance - Automation - Community of practice/centre of excellence ?? 3 core directional guidelines: - A QA mission - A vision that transcends to product quality - A strategy on how to execute ?? 3 QA goals : - Shorten feedback loop a.k.a enable continuous testing in all phases of life cycle. - Around product quality - Team Culture ?? 3 types of annual goals: - Business-driven - Development-driven - Learning goal - mandated every year for my team #QualityEngineering #Teamwork #Goals #Strategy #Automation #QualityAssurance #CommunityOfPractice #Excellence What are your thoughts on structuring quality engineering in sets of three? Let's discuss! ??
要查看或添加评论,请登录
-
As I mentioned a week or so ago, I'll be speaking at QA or the Highway in June! I'm looking forward to presenting "Quality Engineering Bingo Night", in which I'll do my best to "steel man" many of the arguments underpinning the concept of Software Quality Engineering (and other variations on the general idea of shifting testing left, having developers own testing, and any test specialists being in an oversight or coaching role), while also making my case that it still often makes sense to have dedicated testers on a software team. If I had to describe my position on this topic, it would be "yes, and..." as it's described in improv. I like a lot of the general ideas! And I think they help improve the overall quality of our work and the product, as complementary practices to also having specialists committed to expert, deep, exploratory, hands-on, brain-on, eyes-on testing. See you there? #softwaretesting #qualityengineering #conferencetalk #criticalthinking https://lnkd.in/g32E-EfQ
要查看或添加评论,请登录
-
Why working in #documentation topics is needed from the beginning of the project? Even if for some people it is just a formal procedure to close the project, it is important and beneficial to work in documentation since the very beginning. Some reasons are listed below: ??. ???????????????????? ?????? ?????????????? ??????????????????:? ??- Early documentation establishes a clear understanding of project objectives and constraints. This is a key point to be aligned with #ASPICE expectations, while setting the proper way to follow during the rest of the project for everyone involved. ??- Enables alignment with quality goals and facilitates effective testing and validation procedures. ??. ???????? ???????????????????? ?????? ????????????????????: ??- Timely documentation helps identify and address potential challenges before they escalate. With decisions properly documented, there is a lower risk to lose some information if there is some turnover and the reasons for decisions made at the beginning of the project will be always known. ??- Promotes a culture of accountability and transparency within the development team. ??- Safeguards against costly delays and rework, enhancing project efficiency and reliability. Even if producing documentation may be seen as time consuming and introducing delays, it will help in the future to avoid some “archaeology process” to recover why some decisions were made, when and by who. ??. ???????????????? ???????? ?????????????????????????????? ?????? ??????????????????????: ??- Thoughtful documentation of design decisions and coding standards improves code maintainability. It reduces time in the future when needing to rework some SW components of functionalities. Also, it gives some rationales of the taken decisions and may help to evaluate the impact of a rework for a SW component across the rest of the project. ??- Establishes a shared understanding of project architecture and development conventions for everyone in the project and for any assessor that needs to evaluate the status of the project. ??- Simplifies onboarding for new team members and supports future scalability and evolution of the system. Since in almost all projects there is some turnover and some new people during the project’s development, a good documentation becomes necessary for a proper onboard of the newcomers. #SWDevelopmet #Quality #RiskMitigation #Automotive #SWAutomotive
要查看或添加评论,请登录
-
?Challenges in Implementing a Quality Assurance Process in ASPICE: Implementing an effective Quality Assurance (QA) process within the framework of ASPICE (Automotive SPICE) is critical for delivering high-quality, reliable automotive software. However, this journey is not without its challenges: ?? Cultural Shift Towards Quality Shifting the organizational mindset to embrace a quality-first approach can be one of the toughest challenges. Teams often prioritize rapid development and product release over process adherence. Bridging this gap requires: ? Training and awareness programs to instill a culture of quality ? Support from leadership to enforce quality processes over shortcuts ?? Resource Constraints Successful QA requires investment in both skilled personnel and the right tools for reviews, audits, and testing. However, this comes with: ? Challenges in securing budget approval for necessary tools and training ? Strain on the availability of skilled resources, especially in tight project timelines ?? Process Overload and Complexity Mapping ASPICE’s requirements to existing processes without adding unnecessary bureaucracy can overwhelm teams. Common pain points include: ? Integrating ASPICE requirements with agile methodologies ? Avoiding over-documentation, which can slow down development without adding value ?? Cross-functional Collaboration Ensuring quality is not the sole responsibility of QA teams; it requires close collaboration between development, testing, and management. Challenges arise when: ? Teams work in silos, leading to miscommunication and misaligned expectations ? Cross-functional quality initiatives lack visibility or ownership ?? Ongoing Monitoring and Adaptation Quality Assurance isn’t a one-time activity; ASPICE requires continuous monitoring, auditing, and improvement. This includes: ? Maintaining compliance as processes evolve or new requirements emerge ? Regular internal assessments to ensure the QA process stays effective and efficient ?? Balancing Compliance with Innovation Lastly, while compliance is critical, over-focusing on ASPICE requirements can stifle innovation. A key challenge is: ? Finding the sweet spot where innovation can thrive within the boundaries of ASPICE-compliant processes By tackling these challenges with the right strategies, companies can ensure not only compliance but also sustained quality improvement, leading to better customer satisfaction and reliability. ?? What’s been your experience with implementing QA in an ASPICE context? Let’s share insights! ????Please Comment below!! #ASPICE #QualityAssurance #AutomotiveSPICE #SoftwareQuality #ProcessImprovement #Compliance #SoftwareDevelopment
要查看或添加评论,请登录
-
-
Nine months ago, I've posted about how we were able to ???????? 94% ???? ?????? ???????????? ???????????????????? ?????????? when we've implemented test automation: https://lnkd.in/g44P6skg Today, I'm sharing what we're able to do for a project in three months. Agile Testing and Test Automation prove to maximize your resources - time, talent, and money. The key resource here is the talent. Without the proper talent, you cannot fully utilize your time and money. If you need to tap trained and certified Quality Engineering talents who have been using a tried and tested software quality engineering process and standard, just send me a message! #thisisqe360 #qualityengineering #doingmorewithless #softwarequality #softwarequalityengineering #softwaredevelopment
要查看或添加评论,请登录
-
-
Quality engineering is revolutionizing the software testing landscape, ensuring applications meet the highest standards of quality and reliability. Our latest blog delves into the best practices for implementing quality engineering in software testing. Dive into how quality engineering is setting new standards for software excellence. aeriestech.org/QE #QualityEngineering #SoftwareTesting #DigitalInnovation
要查看或添加评论,请登录
-
QA vs QE: Testing vs Engineering. Embedding quality assurance practices at all stages of the SLDC, where everyone plays a part. You as a QE should understand those processes and best practices, guide in their adoption, and procure their adherence. So it goes beyond test planning, execution, troubleshooting and reporting.
Embracing the shift from Quality Assurance to Quality Engineering ???????? The transformation from Quality Assurance (QA) to Quality Engineering (QE) is a significant shift in the approach to software quality. Here's a high-level overview of what this transformation entails: Why Transform from QA to QE? ?Quality Assurance traditionally focuses on identifying defects in software by testing at the end of the development lifecycle. It's often reactive and centered around compliance with predefined standards. ?Quality Engineering, on the other hand, is proactive and strategic. It is a rigorous end-to-end quality check approach, addressing issues in each phase of development to ensure the quality of the product and process. Steps for Transformation: Conduct a Discovery Review: Assess the current state of QA processes and identify areas for improvement. Create a QE Roadmap: Define an end goal and milestones for the transformation, focusing on people, processes, tools, and metrics. Upskill Your Team: Transition roles to support expanded testing techniques by reskilling their existing team to make a successful QA to QE. Benefits of Moving to QE: Faster releases with Agile and DevOps methodologies. Shift left approach, integrating testing with development for early bug detection. Continuous integration (CI) and continuous delivery (CD) for quicker time to market. Quality Engineering is crucial in today's fast-paced and technologically advanced world. It ensures that the rapid development of applications does not compromise their quality. ? #QualityEngineering #ShiftLeft #Innovation #ContinuousImprovement ?#TechTransformation #DigitalTransformation
要查看或添加评论,请登录
-
Quality Assurance: The Heart of Great Products Quality Assurance ensures reliability, builds trust, and turns ideas into flawless execution. ? Why Quality Assurance Matters: Accountability: Guards product integrity. Collaboration: Unites teams for seamless delivery. Improvement: Adopts new tools to meet evolving goals. ? Keys to Quality: Test Early: Spot issues before they grow. Automate Smartly: Save time, boost precision. Focus on Users: Build trust with every test. ?? The Bottom Line: Quality Assurance isn't optional—it's the game-changer for delivering exceptional products. What’s your take on the impact of Quality Assurance in software development? Share your thoughts below! ?? hashtag #Quality Assurance hashtag #Automation hashtag #Innovation hashtag #SoftwareTesting hashtag #Collaboration
要查看或添加评论,请登录
-