Skip to main content

Learning to add tests to a program

https://needpix.com

In order to increase my knowledge, as well as make sure that I can apply the concepts -- I should apply it, correct?  I know this is good advice as a generic, but it didn't work well, in this particular case.

Things started off well:

  • I got permission from someone to add tests to their React app.
  • I got encouragement to add tests to something else,as well (which made me both delighted and a bit scared).
  • I forked the repositories, with promises that I wouldn't add things that would break.
  • Scanned both the code and what the person wanted it to be to used for
  • Chose Jest to get things started - I'd used this before, so it should be easy.

And at this point, I've been stuck.

Do you, dear coder, recognize how many things there are to test in even simple applications? How does one figure out where to start testing, much less make sure that what tests you are doing are effective? And where to start?

Take a deep breath - there are answers out there, and they are good ones, at least to let you figure out what is best for you.

A few acronyms that you are likely going to run into are simple - there are a few that always confuse me before I'm fully in tester mode - AUT is one of them. It's just close enough to a word that the brain tries to make it into a word - then the rest of the sentence is confusing. Most of these can be figured out with a few moments and your favorite search engine (especially if you've been looking at testing topics recently).

My favorite answer is to put myself in the mindset of the person that is going to be using this: What else are they doing? Is this going to be a primary activity, or a quick visit?

And with the advent of foldable phones on the horizon, and three active applications that might exist - where might this be? And is is going to need things that other applications might?

As we have seen, recently, there are many areas of concern that should be tested - and it's good to be aware of them. If you have the time and budget, many of these could be tested. But few have that level of resources and time. So the plan is to get the most important areas tested, and then add as needed.

Simple tools, like Google's Lighthouse and aXe can add a basic level of accessibility confirmation to your work - but these are designed for web pages, and are not always the best tools to use. I use the scales they offer in some contexts to insure that the inward-facing dashboards and alerts are readable.

Working with your security team, or finding those with that skill is becoming a more-vital part of all programs. Everything from injections to securing the code itself in the cloud is now a potential issue: these need to be looked at as important risks to be evaluated.

Now, get into the mindset of your user - what are possibilities that might happen that you don't plan for? Some of these things might be buttons that are close together, or pop-ups that block someone selecting an option they want. And if a finger slides as an option is shown, might the user end up in a place they don't want to be, and can't get out of?

I find myself using April Wenzel's statement of "How can the tech I'm working on be abused?" as a basis for finding things to test - even if the abuse is simply someone tired, distracted, and needing the product now.  

All of these things need looked at - even if they aren't going to have an influence on your application. You may find yourself with a standard list of things to think about as you continue to test - and this isn't bad: just make sure that it continues to grow and change as you do.

Popular posts from this blog

30 Days of Postman - for Testers!

  https://www.pexels.com/photo/white-and-brown-cat-lying-beside-a-laptop-and-toys-5468268/ Photo by Karolina Grabowska from Pexels   Working with developer- focused tools can be a challenge for some testers: we may know what the words mean, but haven't used those skills recently enough to make the tasks simple. Or we may not have ever used them, other than at a quick glance to make sure that what we are getting matches what it should be sending. And some give results that require us to go find another team member to help interpret the results. Being a more-independent tester has always been one of my goals - being able to use the tools that are common in the team, and be able to do at least basic tasks that support my tests with them. Our team used Postman for many of the API tasks that we had, so exploring this tool was a natural fit. There are alternatives it there, both graphical and command line, so feel free to explore! The items that you can do, and tools that help

Thanks Giving 2018

http://thriveology.com/wp-content/uploads/2017/11/ThankfulGrateful.jpg It is that season for we Americans: a time to look back at the past year, and count our blessings.  Thanksgiving has come to mean different things then while I was growing up - the focus is no longer on what has gone right, but what wrongs were (and, in some cases continue to be) done. I try and focus on what I can do to minimize the wrong, and accept that the past has happened. And then the fun begins - finding all the things to be thankful for! Things have been rocky, at points this year, I'm still unemployed for money, and have had some serious personal issues arise and be dealt with. But, all in all, I think the bad is outweighed by the good.  This has been a year of changes: not only have I given up on trying to go back to the way things used to be, I have moved forward - supported, encouraged, and occasionally pulled - into a future that I just now am starting to feel I deserve. I still am

Where Is It? Part 1 - Inputs

Photo by Pixabay from Pexels     I am job-searching, and running into some coding challenges. Most of them are simple - some seem to want one-line solutions that require two cups of coffee and a half-hour to figure out what they want. Others are far above where my skills lie, and these I give a try for, and learn. And then there are the ones that offer, seemingly randomly, a challenge - within my skills (or at least my research skills) - that could be used as part of a larger project that I want to work on. This was the case last week, when I tried for a position that was a bit above what I felt I could do comfortably. The challenge was to let someone enter items, and then give back their location. In a language I am just familiar enough to be a danger to myself in. Happily, and thinking forward about how I could use this as a part of a larger program that would  use something like this to interact with the user. And also, this is command line, and thinking of how to set this up to