If you want to get started in Test Automation, then I find jumping straight into it is the fastest way to learn. Some might suggest you need a certain level of coding knowledge before designing a well constructed automation pack, while I agree that a level of coding knowledge is going to allow you to build a robust framework that is easy to maintain, jumping right into writing automation will quickly give you a foundation which you can build upon.
Sometimes you are tasked with testing a product or feature that has a lack of documentation and requirements. When we are lacking this information it can be tough to work out if what we are seeing is expected. You really need a clear way to recognise problems with your application.
Test Oracles are a mechanism that we can use to work out some truths in the product or feature. We compare the output from the application, to the oracles we have gathered.
Exploratory software testing is an approach that can help uncover bugs quickly. It is described as simultaneously learning, test design, analysing and executing tests.
A “tour” is an exploration of a product that is organised around a theme. You decide on a theme, then navigate and tour around the application to document your theme findings. Tours are excellent for surfacing a collection of ideas, that you can then explore in depth, one at a time.
In my work, I do a lot of API and Web Service testing. Most of the Web Services we create are brand new; we collaborate on what the service should do, what type of technologies are used, and the standard we will be using i.e RESTful.
There are many ways to create a successful mind map for testing an application, feature or product. In this blog post, we will look through a couple of ways to help document, execute, report and collaborate my testing efforts.
Mnemonics are rhymes or acronyms, these are used to help memorise long, complicated or complex things. Generally it’s easier to memorise a rhythm or acronym and then use that to fill out the information that is associated with that rhyme or acronym. It is used as a memory aid.
There are a lot of testing techniques which can be applied while testing a product or application. The techniques used is context dependent, meaning it depends on what you are testing.
While a testing technique might work well in one situation, it may not be suitable in another. It is important to know many different testing techniques so that you can apply the right ones, in the right situation.
Build the product right while building the right product
Acceptance criteria are an important part to the iterative planning process when working under an agile methodology. Having clearly defined acceptance criteria, that are written in line with your user stories, is an essential way to ensure you and your team know when the story has been completed.
Many organisations are moving towards an Agile approach to the work environment; instead of having teams consisting purely of testers, the teams are now set up consisting of multiple functions. An example of an agile team is one which could consist of Developers, a Business Analyst, Product Owner and a Tester. While there are many benefits to this approach, such as the ability to work with all roles when thinking, designing and creating features or products, a challenge has been ensuring the internal testing community is still able to engage with each other regularly.
Bug Magnet is an open source Chrome and Firefox extension created by Gojko Adzic, that stores a set of heuristics that can be used for testing web applications.
Bug Magnet stores values and edge cases that are common causes of failures for input fields, text areas, content editable DIVs. Some examples are: