Smart Development Testing

GREAT QUALITY CODE IS NOT THE RESULT OF INTENSE SYSTEM TESTING

It is the result of well structured filtration of issues from early stage

IT IS NOT BLIND AUTOMATION THAT FINDS DEFECTS, IT IS SMART TESTS

Be purposeful as to what issues you want to uncover. Then figure how you can do this efficiently.

BE LEAN. STAY CLEAN.

Lean is about producing less waste. Prevent smartly. Test minimally. Automate what you have to test maximally.

#SMARTDEVTEST

Supercharge your 'unit test' pratice enabling developers to validate their code rapidly, effectively and most improtantly without disrupting the rhythm of coding

SmartDevTest Practice

We all intuitively know that good quality at an early stage goes a long way in delivering great code rapidly and
optimally. After all, who would not want a solid foundation for a complex product. Testing building blocks should
be easy and quick, in reality this is probably not all well done as it should be. A smart lightweight approach that
does not create more work for developers or upset the development rhythm is what is paramount to success.
And this is precisely what SmartDevTest strives to accomplish.

THE BUSINESS CHALLENGE

A compromised ‘unit test’ puts unnecessary strain on QA folks who seem to be compelled to go after these issues at the expense of system test resulting in not-so stunning quality of delivered software.

Developers do not deliberately write bad code, it is just that accidents happen. Accidents happen due to very many reasons: push of impractical unit testing, automation without good dev test cases, emphasis on dynamic testing when static methods could be as effective.

Finally the mother of all reasons, of not being sharp and purposeful as to what type of defects need to be the focus of “unit testing” or sensitisation for prevention.

WHAT IS SMARTDEVTEST

SmartDevTest is a service offering that supercharges your ‘unit test’ practice enabling developers to validate their code rapidly, effectively and most importantly without disrupting the rhythm of coding.

SmartDevTest is based on lean philosophy that focuses on being sensitive to prevent issues, being goal focused as to the type of issues to uncover, staying sharp to detect early, using light aids to do easily, and resorting to automation only for value-adding complex repeatable tests.

It is a harmonious blend of scientific thinking, smart aids, rapid process, sensible automation, static assessment and dynamic testing to test less and accomplish more.

BUSINESS OUTCOMES

The outcomes to be expected are heightened awareness to ‘defects’ by developers, a consistent effective DevTest practice, drop in leakage of dev-defects to QA and better early stage quality code.

Sensitisation to the types of defects is what enables a good defensive coding mentality and test driven approach. Focus on behavior model, enables a BDD style approach to design and automation. Value based approach enables a sensible mix of static and dynamic (automated) tests.

The significant outcome is freeing up the QA/testers to focus on what they do best, of testing the system from an entire product/app and user-usage view.

THE SERVICE OFFERING

The service offering consists of experiential workshop and online learning capsules to enable you to reorient your DevTest so that you “Test less, accomplish more”.

It also includes SmartDevCheck, a smart checklist to help you perform static evaluation, sensitise you to prevent rather than only test and make you think.

A super light personal process to foster rapid testing and a guideline based on TestPyramid to help you automate what is value adding especially at top of the pyramid.

Learn how to “Test less, Accomplish more”
Test statically, Sensitise & Prevent
Test rapidly, Automate meaningfully

ENGAGEMENT MODEL

This is a result oriented SIX to EIGHT weeks program, consisting of assessment, orientation and then implementation/support.

Week#1: Assess state of practice of dev test via discussions with team members, analyse defects/test cases, create assessment report, the initial baseline.

Week#2: 1-day instructor led experiential workshop that outlines key concepts, with two How-to-do sessions, followed with an online course to be taken by participants.

Week 3-6(8): Developers implement this with STAG tracking, assisting, fine-tuning. The final outcomes are compared against the original assessment report.