SQA

What inconsistent UI behaviour tells us about software quality management

·5 min read

On a recent engagement, I raised a question about how part of the user interface behaved. At the time I didn't notice anything unusual in the client QA's reaction. That night, during my usual review of the day, I realised what I had missed. It is a somewhat unusual case in software quality, so I want to share it here.


A confused user facing the same controls behaving differently
So how am I supposed to use this?

Multiple code branches to react the same interactions
A tangle of reinvented wheels leaks the development team's secrets through all sorts of small details

Risks at the source code level

  • Higher chance of defects: several implementations of similar functionality means each one can carry its own bugs.
  • Harder testing: when the same functionality has several behaviour patterns, test coverage gets more complicated.
  • Duplicated code: different implementation paths can lead to duplicated code, which raises the risk of changing one place and missing the other.

Maintainability and sustaining quality

  • Higher maintenance cost: changing one feature may mean tracking down several implementations, which increases the chance of missing something.
  • Knock-on effects: when a feature changes, inconsistent implementations easily cause unexpected side effects.
  • Faster quality decay: over time and across iterations, inconsistencies tend to grow, and quality degrades faster.

Quality assurance strategies

Systematic quality control

For behavioural consistency in the interface, we need systematic quality controls:

  • Make behavioural consistency part of acceptance criteria: beyond the functional spec, state explicitly that similar elements must behave the same way.
  • Add consistency checkpoints to code review: during review, pay specific attention to whether similar features are implemented the same way.
  • Automate tests for behavioural consistency: write test scripts that check whether interface elements behave with the expected consistency.

Quality at the architecture level

To fix consistency problems at the root, start from the architecture:

  • Standardise and reuse components: build standard components for common UI elements so their behaviour is uniform.
  • One event handling mechanism: set up a centralised event handling framework so similar events are always handled the same way.
  • Think about quality and architecture together: consider behavioural consistency during architecture design, instead of treating it as a purely UI matter.

Improving the quality process

At the process level, we can do the following:

  • Make the QA team more alert to consistency issues: train QA staff to spot and report inconsistencies, like the QA in our case.
  • Add consistency checkpoints to dev and test collaboration: start discussing behavioural consistency early in development.
  • Collect cases and refine standards: build a library of inconsistency issues and keep improving the related quality standards.

Finally…

Behavioural consistency in a user interface looks like a surface matter, but it is how the software's internal quality shows on the outside. Our case is small, yet it reveals a potential systemic quality problem. By paying attention to small everyday cases like this, we can find and fix deeper quality risks.

Need Professional Assistance?

Our team are senior engineers and former executives with 20+ years in commercial product development — from apps serving hundreds of millions of users to B2B SaaS platforms serving tens of thousands of merchants. In recent years the focus has been enterprise AI adoption, from mapping the opportunity through to tuning what is live. Whether that means:

  • Mapping AI opportunities and sequencing them
  • Preparing data flows and integrating existing systems
  • Building forecasting and optimisation models
  • Monitoring and tuning after go-live
  • Test strategy and process review
  • Building and adopting test automation

We can provide professional advice and concrete solutions for teams of different scales and types. If you're facing similar challenges, feel free tocontact our consulting team.