Skip to main content

Good QA Assignment: You may Want to Ask in Your Interviews

QA position is not like development or analysis position so finding a good QA engineer is not as easy as development engineer. You may ask some technical questions to your QA candidate but half of the QA responsible is related to social ability, and the rest part is related to knowledge about testing domain and practices. I want to share a good review question and a related answers below.

Question:

Before you start- some directions:
  • You need a computer, it can be a Windows XP/Vista/Windows 7, or a Mac OSX/Linux machine, of course 
  • Download the KeePass installer and install it on your machine you intend to test with, install the Classic Edition Version 1.17 from: http://keepass.info/download.html
  • The problem:

    KeePass Password Safe is a free, open source, light-weight and easy-to-use password manager for Windows. You can store your passwords in a highly-encrypted database, which is locked with one master password or key file.

    Part 1:

    Use your skills as a tester to produce a report (in the format of your choice) using the word processor of your choice.
    The format should be able to be printed upon completion. The report should contain the following at a minimum
  • An overview of the approach you took to your testing and why
  • All possible high-level scenarios for key functionalities of this system
  • Test cases for 1 functionality you within the above key functionalities you have chosen
  • Part 2:


    The KeePass software is about to introduce new functionality:

    When setting a new master key the user will have the option of entering text into a text box to act as a password reminder.

    When logging into a password database the user will be able to click a button to display the password tip.

    Using your word processor of your choice, create a document to list:
  • Any confusions you might have about this new functionality and assumptions
  • What tests you would carry out when this new functionality is delivered based on your assumption
  • Environment/Tools you would need to assist you testing

  • A Related Answer


    Question 1

    Approach: Rapid Testing use Exploratory Testing as method

    Exploratory Testing
  • What's it about
  • Divide your application into testable parts
  • Set a session for every part of app. i.e.: 60mins for setting password
  • Set a succes point for every session
  • Test the parts throughout each session, repeat the cycle

  • Cycle
  • test it
  • learn it
  • test it
  • if bug occurs just write down, don't waste time for documentation

  • Report your bug at end of the session
  • just enough documentation

  • Why the ET
  • I don't know the app.
  • I have just little time to learn
  • I have learn it during testing and then test it better
  • there is no requirement for the app
  • as a tester my mission is to find the bugs which is critical first

  • Application of the Approach

  • We have 5 parts
  • Every parts has different number of sessions i.e. "File" has 3 sessions
  • every session should be 10 mins

  • Parts of Application
  • File
  • New
  • Open
  • Close
  • Save
  • Save As
  • Database Setting
  • Change Master Key
  • Print preview
  • Print
  • Import
  • Export
  • Lock Workspace
  • Exit

  • Edit
  • View
  • Tools
  • Password Generator
  • TAN wizard
  • Repair KeePass database
  • Show expired Entries
  • Plugins
  • Options
  • Help


  • Sessions
  • Prioritize the Parts of Application
  •                  Note: Test this order. Order of the color; Red, yellow, blue, green.

  • File
  • New
  • Open
  • Close
  • Save
  • Save As
  • Database Setting
  • Change Master Key
  • Print preview
  • Print
  • Import
  • Export
  • Lock Workspace
  • Exit


  • Sample Test Cases
  • Creating new password database
  • Negatif
  • tc1
  • click File > New
  • click cancel
  • see blank page

  • tc2
  • click File > New
  • type "m" then press "ok"
  • type "n" then press "ok"
  • see "password and repeated password aren't identical"
  • press enter
  • type "n" then press "ok"
  • see "password and repeated password aren't identical"
  • press enter
  • type "n" then press "ok"
  • see "password and repeated password aren't identical"
  • press enter
  • see blank page

  • tc3
  • ...

  • Positive
  • tc4
  • click File > New
  • type "m" then press "ok"
  • type "m" then press "ok"
  • Boundary

  • tc5
  • click File > New
  • type nothing then press "ok"
  • see "EITHER enter a password or select a file"
  • press "ok" and the "cancel"
  • see blank page

  • tc6
  • click File > New
  • type 9999bit characters then press "ok"
  • type the same characters then press "ok"
  • see that the password is accepted
  • try this for longer pass as much as your system let you enter
  • see that there is no upper boundary for simple test environment
  • Question 2

    1. Test Analysis

  • entry check: numeric, alphanumeric or no restriction
  • number of characters: upper and lower boundary
  • can password be used as reminder
  • does it mandatory to use reminder
    1. Test Design

  • positive test cases
  • Negative test cases
  • Boundary test cases
  • and regression test cases as tc1 to tc6 to check if the system is OK
    1. Tool Support

  • Test data generator
  • Password
  • reminder
  • Automation tools
  • Automating regression test cases

  • You can also check the mind map file below.






    Popular posts for software testing and automation

    Selenium Error "Element is not currently interactable and may not be manipulated"

    Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

    Change Default Timeout and Wait Time of Capybara

    One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

    Page-Object Pattern for Selenium Test Automation with Python

    Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the

    Create an Alias for Interactive Console Work: Selenium and Capybara

    If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

    Performance Testing on CI: Locust is running on Jenkins

    For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so