- Analyzing the functional specification.

- Identifying the requirements.

- Creating Requirements, Test Plan (scripts), Test Lab (holding scripts to be run) and Defects with the use of 'Mercury Quality Center v9.1 (formally Test Director)'.

- Creating automated browser test scripts for Mozilla Firefox with the use of Selenium IDE.

- Creating storys and highlighting requirements with the use of Jira, Confluence and Mingle

- Using Postman and Swagger for creating API's to transfer data to various platforms.

- Confirming the passing of data via the MuleSoft platform.

- Checking data can get passed to and from various platforms including Salesforce.

- Testing of the Financial Information Services, used to calculate awards dependant on the data and settings.

- Regular usage of MS Teams for meetings

- Testing of the OpenAM component to manage user access and privileges.

- Creation and editing of XML files so as to simulate the use of required data associated with the document creation under test.

- Processing of XML files through the Doc Management lifecycle in order to confirm system requirements have been met using PuTTY (UNIX environment) for running scripts to process documents sent from the front end client application

- WinSCP v3.8.2 for locating and editing the xml file processed and created by PuTTY and to be held within documents under test.

- Querying of the Oracle Database for test data and resulting data with the use of Toad for Oracle v9.0.0.160 (by Quest Software)

- GSView32 v4.6 (a Ghost Script Graphical Interface application for converting the large postscript files created during testing, into smaller more manageable PDF files for viewing and comparing)

- Adobe Acrobat 7 and 8 for comparing documents under test and creating test results

- Reporting of results to development team and management in order for the latest release to be set live

- Serena ChangeMan Version Manager v8.1.4.2 for managing functional specifications and document/project management

- IBM Lotus Notes v7 used for emails, meetings, and document reviewing system

- Working on front end client web sites for organizations such as (Ted Baker, All Saints, Day Birger, Nigel Hall, Reiss, Bench, Gant, Elvis Jesus, Versatile Apparel) along with Enrich server settings.

- Analyzing the requirements.

- Creation of test scripts obtained from development/project info.

- Running of test scripts within various web browsers (Internet Explorer, Firefox, Opera, Safari, and Google).

- Raising of defects with the aid of Mantis Bug Tracker and assigning to the developer concerned.

- Re-running of test script after fix and running of yet to be run test script.

- Running of general regression functionality.

- Creation of test reports after each clients release, involving requirements met, scripts passed and failed, defects associated and un-associated with the requirements raised, current defects status, priority and severity.

While working within the client site of The National Australia Banking Group, responsibilities have involved:

- Understanding of project lifecycle and deliverables.

- Providing input and expertise into test approach and direction based on experience and expertise in solution or technologies being implemented.

- Contributing to Overall Test Strategies and Master Test Plans where required.

- Liaising with Business and Development teams in order to ensure quality of test scripts and timely resolution of defects and issues

- Reviewing of design and requirements documentation in order to prepare test scripts.

- Preparing test scripts for execution by Test Team with the use of Mercury (Quality Center Test Director 9.0)

- Preparing and executing test sets against the application under test using prepared test scripts.

- Keeping a record of progress against plan

- Identifying and recording of defects found during the execution of test scripts.

- Communicating and presenting information and status reports to team members and external teams.

- Reviewing work of others providing constructive feedback.

- Working under limited supervision.

- Planning and controlling own work flow to ensure all deadlines are met and managing own tasks effectively.

- Ensuring all work is carried out and documented in accordance with required standards, methods and procedures to ensure information retention and re-use.

Within the first project I was solely responsible for the testing which involved the analysis of the functional specification for a proposed on line customer information systems for use within Airdrie Savings Bank This was followed by the creation of test scripts and scenarios to confirm the released build of the system met the proposals detailed within the functional specification. Development was undertaken by a 3rd party developer and communication had to be regularly carried out between myself, development and the on site customer themselves.

Responsibilities involved the analysis of the functional specification for a proposed information system. The Inisoft Software 'Relatis' platform worked as an on line go between for the transferral and display of requested financial information between the customer and the Airdrie Savings Bank (ASB). Test Scripting and bug management was carried out with the aid of Test Controller along with automation with the help of Badboy and NetVantage

My second project involved the testing of an upgrade to an existing in-house product associated with Call Centre Processes and Management on a platform known as synTelate which is a screen customization and callflow tool for use on the call centre agent desktop. This again involved the complete testing lifecycle from:

- Analyzing the functional specification

- Identifying the requirements

- Creation of scripts to associate with the requirements

- Installing of builds

- Running of scripts

- Raising and reporting of defects.

This was then followed by the running of regression scripts to confirm, no functionality had been unexpectedly affected by the latest upgrade/changes to the existing system. Database checks had to be carried on the following:

- Oracle SQL Developer DB

- SQL Server 2005 / SQL Server Management Studio

Responsibilities involved the caring of the elderly including all aspects of day to day life.

Responsibilities involved the analysis of the functional specification for a proposed communication system requested by the Engineering/Building trade. The Mclaren Software platform 'Enterprises Engineer' works as a go between for the transferral and display of requested information from various sources in the Engineering/Building lifecycle, including digital design documentation (Documentum & FileNET) and imagery (AutoCAD & MicroStation); all of which can be tracked and managed via internal audit.

Test scripting followed the analysis of the proposed systems functional specification which was then followed by the creation and running of scripts along with the reporting of errors/defects to the in house team of developers.

Test Scripting was carried out with the aid of 'Test Director' with Bug management and reporting aided with the use of 'Documentum Workspace'

- Mercury Test Director 8.0

- Mercury (Quality Center) Test Director 9.0

- VMware

Responsibilities involve working in close contact with the development side of the environment on a multi tiered system dealing with financial account and lending facilities.

This is taking into consideration the System, User Acceptance Testing processes and tools to quickly develop test plans and scripts. Together, with the transferral of knowledge to colleagues for the benefit of the HFC projects as a whole in the near future.

Errors encouintered would be logged within 'Rational Clear Quest' and assigned to the specific department responsible whether it be in house or external third party.

Responsibilities involved working in support of the UK governmental Department for Work and Pensions (DWP) on the Personal Details Repository (PDR) and latterly Pensions Forecasting System (PFS) projects, specifically within the Systems Test environments.

Here I was responsible for building knowledge of the DWP customer business and also the System Test processes and tools to quickly develop test plans and scripts. Along with this was the carrying out the transferral of knowledge to the benefit of the PFS project in the functionality complex Calculation (of entitlement to benefit) test team.

Electronic Data Systems (EDS) were involved in a long-term, high profile, political contract involving the in house development and management of a web based Court Services information system. This applied to the regional courts and related departments throughout England and Wales. based Court Services information system. This applied to the regional courts and related departments throughout England and Wales.

Responsibility lay for System, User Acceptance, Regression Testing and general Quality Assurance, examining existing and proposed functional requirements of a totally bespoke area of the system, developed by an external 3rd party development team.

Data entered via the web based GUI would then be confirmed using SQL to query the database. It involves the use of web technology enabling Claimants or Solicitors to put forward a financial claim against a defendant; without having to go through the typical manual court process www.moneyclaim.gov.uk.

This involves a nation wide WAN of I.P. addressed components and systems both old and new, which must have no effect on the existing system and be up and running within tight deadlines.

Tools used to simulate certain processes and aid management include:

- Compuware QA Run

- PVCS Tracker.

Responsibility arose for the Quality Assurance (QA) of the in house Central Lending Platform Delivery Program on the Lloyds TSB account situated in Peterlee, Durham. The purpose of the CLP Delivery Program is to deliver additional functionality to the existing, EDS Personal Loan Servicing Centre (PLSC) which relies on a range of nation wide network functionalities.

The PLSC is capable of dealing with the complete loan lifecycle process, from initial indicative quotations to draw down of funds, as well as the ongoing servicing of accounts. The centre is also capable of aiding set up and care of loans originating from the LTSB branch systems as well as being responsible for supporting all the service delivery channels, including telephone, post and the web.

Responsibilities within the role mainly involved the QA of the LTSB Central Lending Platform both branch simulation (UNIX environment) and call centre systems. This involved carrying out manual testing, of the existing and soon to be released Unit, System and Acceptance environments. UNIX black box testing was also carried out within Regression to confirm newly entered data into the current platform/system could be queries via the new third party GUI.

Responsibilities also involved the creation and upkeep of documentation to aid current and future employees understand the testing environments and associated components (e.g. Pan Credit).

The logging of faults was carried out with the aid of Mercury Test Director application.

ComponentSource were a fairly new organisation who were relying on public and corporate purchases of software components from the web site. The testing of this system, which was based in-house, focused on System, User Acceptance Testing(UAT) and Regression, with user friendliness and ease of use being the main requirement. The testing took place within a rapidly changing environment, which relied on financial exchanges of Personal Computer Electronic Financial Transfer (PCEFT) occurring via Internet Service Providers on both Internet Explorer and Netscape Navigator Platforms, which also gave rise to security issues such as fire walls, cookies etc. The automated testing tools used included:

- Astra Quick Test

- RSW e-test

These initially involve the manual recording of test scripts, followed by the assigning of parameters. These test scripts however, have to be updated on almost every new release of the system; apart from when it was concerning Regression as this is dealing with existing system functionality which should not have changed since the last successful release. Error logging software used was:

- Mercury Test Director