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.






    Comments

    Popular posts from this blog

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

    Change Default Timeout and Wait Time of Capybara

    Page-Object Pattern for Selenium Test Automation with Python

    Performance Testing on CI: Locust is running on Jenkins

    How to Set Shared Preferences in Espresso Test for Kotlin and Java