A discussion on TWIT had me wondering what 'Grey Box Testing' was. Luckily, some lovely people were on hand to answer my question!

Grey box testing combines both white box (internal knowledge) and black box (external perspective) testing methods.

Great Re-Testbash session online with the MoT community and I wrote the following virtual post it note.

Debrief the week in testing

Is this now a ringtone?....can someone please remix this for the next MOT London lol I had similar thoughts to Aj Wilson, who commented on Christine Pinto's kind post about Rosie Sherry. https:...

Is the future of test case management at risk? Let's go exploring.

63% of you were not aware of the existence of the Staff Quality Engineer role

Internationalisation Testing aims to build globally-ready software that can easily adapt to any market’s cultural, linguistic, or legal requirements. Different to Localisation Testing which takes an Internationalised product and adapts its contents (whether text, image, sound, or color) to maximize its chances of success in the target market.A good example of this is Global eCommerce retail websites for fashion. For Internationalisation Testing good stakeholder discovery engagement would be Code Architects, Head of Global Product, Performance Marketing Teams or Trade Optimisation specialists for the brand. 

This debate explored the role of quality coaching, how it differs from quality engineering and where it is most effective

Also known as "Tech Debt" in the context of Continuous Testing, Holistic Testing and DevOps. Tech debt is a metaphor for the engineering quality trade-offs developers, testers and business stakeholders make to meet schedules and customer expectations.  Types: There are various different types of tech debt, such as intentional vs. unintentional tech debt.  Intentional debt is taken on knowingly to meet deadlines. Unintentional debt arises from poor practices, time constraints or lack of knowledge.  Morale impact: Tech debt can also affect the development team's morale and productivity. Working with a codebase that is difficult to maintain, or in a team where value being delivered is ignored, can be frustrating and demotivating.Financial costs: Over time, tech debt can lead to increased costs due to the need for more extensive refactoring or even complete rewrites. This can impact the overall budget and financial planning of a project.Examples of tech debt: hard-coded values, lack of the right level of documentation, no test automation frameworks or poor architecture decisions.Strategies for managing tech debt: This should include ways to manage and reduce technical debt, such as regular code reviews, refactoring sessions, and adopting best practices, risk storming, shifting left and right where appropriate can make the domain or teams definition more actionable.

Remit: Someone who is proficient across various testing methodologies, such as exploratory testing, performance testing, security testing, and automation. This versatility allows them to tackle a wide range of challenges and adapt to different situations. Not just having read about different types of testing - but has active experience doing them.Hiring skills: broad technical knowledge, adaptability, problem-solving, communication, critical thinking, basic project management, attention to detail, continuous learning, collaboration, flexibility. Pros: Being proficient in diverse methodologies equips you to tackle any challenge that comes your way. The need to stay updated across multiple fields encourages continuous learning and professional growth, keeping generalists engaged and knowledgeable about the latest trends and technologies. This can signal roots in leadership potential. Value: Generalists are particularly valuable early on because they can speak to and work on different types of testing, which is great for setting out a holistic strategy for testing. IMO, many of the better senior testers tend to be generalists as this allows them to help in many different areas. It’s about knowing when to go deep, when to go wide and when to have the sweet spot.Cons: Some can have a lack of deep expertise - this can be a disadvantage when tackling complex, niche problems that require in-depth understanding. However this is not always the case. Should be measured via the individual.  Difficulty in staying updated or potential for overwhelm. You may hear or see the term "jack of all trades, master of none".