Lecture 6 - Classifying the Most Common Types of Testing -> Quick Intro -> By Knowledge Of The Internals Of The Software -> By The Object Of Testing -> By Time Of Test Execution -> By Positivism Of Test Scenarios -> By Degree Of Isolation Of Tested Components -> By Degree Of Automation -> By Preparedness– Manual testing
– Semi-automated testing
– Automated testing
This is testing without the help of any test automation programs. The testing techniques for manual functional testing are core elements of black box testing methodology.
This is manual testing done with partial usage of the test automation, usually in form of helpers. For example, you can automatically generate a new user account with Account Creator and manually add a book to the shopping cart. Test Case with Credit Card is typical example of semi-automated testing.
Talking about Account Creator, I want to give you quick tip about the test password.
BTW
It’s a really good idea to have a convention for default password for test accounts within the company. As you know, ShareLane’s convention is “1111”.
Why is this a good idea? Sometimes you don’t have time to create a new user account with sophisticated settings. In the case of ShareLane, all user accounts are the same. But in the case of sophisticated products like financial software, testers can spend a lot of time creating necessary user accounts of a particular variety. Therefore, in some cases you might want to reuse an existing test user account. The problem is that if you remember the username but have forgotten the password, it’s not easy to recover it because passwords are usually encrypted in the DB. But if you have a password convention, you don’t even have to guess what the password is.
Another situation when having a password convention looks attractive is an exchange of information – e.g., when you give the developer info regarding the user account, he won’t need to remember the password.
As always, a warning: if you reuse an account that was created by another tester, make sure to get his permission.
This is testing completely done by running test automation tools. QA automation can be done with simple tools like link checkers or by writing sophisticated automation scripts using automation frameworks (unittest, nose) and special libraries (Selenium) Next ->
Lecture 6 - Classifying the Most Common Types of Testing -> Quick Intro -> By Knowledge Of The Internals Of The Software -> By The Object Of Testing -> By Time Of Test Execution -> By Positivism Of Test Scenarios -> By Degree Of Isolation Of Tested Components -> By Degree Of Automation -> By Preparedness
