Selenium Notes

Automated testing: The process of reducing and where possible removing human interactions from an existing manual test process. Automated Manual Repeatability Easy to pass or fail a test case Unlikely to change Ran often Quality over quantity Able to test unique features Able to detect and test ambiguous features. Benefits: Improves the accuracy and reliability […]

Change Requests

A change request is an additional piece of work to be completed by the development team that was outside the original scope of the project. This may be a change to the current functionality or an addition of completely new functionality. Change request raised > seek approvals > impact analysis > accept or reject work

Sanity Testing

The purpose of sanity testing is to verify added and updated functionality such as bug fixes and software updates. Sanity testing is performed by the testers and cannot be automated. It is considered to be a narrow and deep approach, like a specialised health check-up.

Smoke Testing

The purpose is to verify the basic or critical existing functionality of an application. It is performed by testers and developers. Smoke testing may be automated and follows a shallow and wide approach, like a general health check-up.

Test Scripting

Scripted: everything is planned and written out. Unscripted: no documentation, usually experience based. Manual non-exploratory: strictly manual testing. Manual exploratory: unscripted; test execution logging and learning are done simultaneously Automated: manual testing instructions are recorded and ran. Session based: time boxed session of exploratory testing


Agile development is an iterative process which focuses on the development team working in a flexible environment, in this model use the entire project team works in cycles toward demonstrable quality. There are four main approaches when working in agile: RAD or rapid action development, this way of software development includes no planning in advance, […]

Test Cases

Each test case should consist of sections covering: the test case ID, priority, test condition, test data, test steps expected results, actual results and defect id. The four main beliefs are agile are: Individuals and interactions over process and tools Working deliverables over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following […]