Software Testing...

Everyone is a tester in our day-to-day life without our knowledge irrespective of the technology we use. We do web application, mobile, and desktop testing to connect the world.

“Testing is the process of evaluating a product by learning about it through experiencing, exploring, and experimenting, which includes to some degree: questioning, study, modeling, observation, inference, etc.” -  James Bach and Michael Bolton



Let me take an example. Nowadays, it is our first ritual or habit to check our mobile phone after we open our eyes or even before we hear the alarm. We have a separate inseparable bond with it. You might be shocked if the alarm is not ringing up correctly and you missed waking up. It might delay your daily routine. Right?

Below are a few checkpoints you should verify before you go to bed.

ü  Select the present time zone

ü  Correct date and time to set up an alarm

ü  Enable the alarm option

ü  The alarm volume is not silent

ü  Select vibration mode as per your wish

ü  Select the alarm ringtone

ü  Enable the Snooze option as per your wish

ü  The mobile phone has enough battery life

But, how does a tester test these functionalities? Here is a quick overview!


Alarm Setting: Ability to set alarms for a specific time, recurring times (daily/weekly), one-time alarm

Time accuracy: Ability to trigger the alarms in different states such as sleep mode, undisturbed mode, locked, and silent mode.

Alarm volume: Test the volume to be heard clearly when the alarm rings at various levels with accuracy.

Vibration: Ensure the vibration has been enabled based on the user’s requirement. It’s an alternate way to wake you up.

Snooze function: If you are a snoozing lover, it should be verified to help the user snooze multiple times for a preset or customized duration.

Dismissal: Make sure the alarm can be dismissed easily when it is no longer needed.

Multiple alarms: Potential to set multiple alarms for different times and days.

Display: Verify the alarm information (time, label) displays correctly on the screen when it triggers

Customization: A user can able to customize the date, time, and labels based on their requirement

Battery consumption: Test the impact of alarm setting on battery life and make sure it does not excessively drain due to alarm setting.

Alarm sound selection: Able to change the alarm sounds or customized tones in the mobile phone.

Alarm while on call: Test the alarm triggers when the user is on call or how the system behaves.

Accessibility: Test the alarm is accessible to users with disabilities such as screen readings or accessibility settings.

Integration with the clock app: Ensure the alarm is set through the clock application or any other integrated app.

Testing across OS versions: Perform the alarm setting in different OS versions to ensure compatibility.

Testing on different devices: Test on various devices to ensure the alarm functionality works seamlessly.

Edge cases: Test the alarm in different time zones and daylight savings situations.

We do testing every day but how to test an application is where the software tester stands individually. Software testers should be skilled in a way to ensure the quality of the applications they test. Learning this skill is not rocket science. However, learning how to do it correctly is the technique one should know.


Comments

Popular posts from this blog

How to Install Jenkins

HTTP Payloads

Variables in Postman