Quick Video about Software Testing on Facebook (Selenium on Facebook)

What I took from IT Security and used on QA Testing

I have met over the years many types of testers. Many types of professionals, with various core skills. Overall, they all fill a group that aims for the same objective, and together, with those various skills, create a more effective team.

I have a developer and very technical background, and worked on IT Security as well. I have brought many of my experiences from there to the Quality Assurance world.

Deep understanding of software, and SFDC, is also a key factor to complement your professional profile, ultimately helping you to be more effective and even efficient, because you may know where to look for bugs, errors, mistakes, and may know in advance how to trigger them due to your experience.

Some of the things I took from IT Security:

• Breaking software, files, outputs, packets, formats.
• Secure code.
• Validate all inputs, always, from everyone.
• Pay extra attention to how the memory is being used/managed. This greatly changes from language to language.
• Certain non-functional requirements, often not defined, can make a difference for the acceptance criteria of any software development.

QA Automation Testing Introduction

This blog aims to share information and knowledge about QA, Testing, and Testing Automation.

Even though there are lots of blogs, books, websites and available information on the subject out there, my goal is to keep this content clear, specific and summarized, in the hopes of be a reference in the future for certain cases, for myself and others.

Testing is always needed to ensure that what we are creating or developing works as it should, from a functional perspective (if we are using verification (did we build the product right?) and also, very often, if it is what the end-user, customer or client really required and needed (validation (did we build the right product?)), and with the desired quality.

Testing Automation, also referred just as "automation", is the application of automation processes to perform testing. In Testing, we find that certain tests need to be repeated often and might be simple and/or time consuming. If, for example, you ever worked in a project and needed to perform testing and QA, you know how automation would be useful when performing a regression. This is more notorious on environments and projects where you have new versions and sub-versions of the software often, such as in projects using agile methodologies.