- 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

Position: Test Analyst- Working on front end client web sites- Analyzing the requirements.- Creation of test scripts obtained from development/project info.- Running of test scripts.- Raising of defects with the aid of Mantis Bug Tracker (http://www.mantisbt.org/) 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 and 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 www.airdriesavingsbank.com/pb-internet-banking . 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 organization and communication had to be regularly carried out between myself, development and the on site customer themselves. 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 www.inisoft.co.uk/syntelate.html . 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 build 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 involve the caring for 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 transfer and display of requested information from various sources in the Engineering/Building lifecycle, including digital design documentation (Documentum) and imagery (AutoCAD); all of which can be tracked via internal audit and managed. Test scripting has followed the analysis of the proposed systems functional specification followed by the creation and running of scripts along with the reporting of errors/bugs to the in house team of developers. Test Script creation 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 involved the analysis and quality assurance of an in house lending platform (Compass) which could be used on a national basis linked to various components and servers from third party organisations in order to carry out the credit checking of individuals and related properties and locations (e.g. Equifax and Experian Credit Enquiry Database). Major segments of the role centred on analysing the functional specification of the proposed release, followed by the creation and running of scripts in which to confirm the expected outcomes. Errors would then be logged within 'Rational Clear Quest' and assigned to the specific department responsible whether it be in house or external third party. - Rational Clear Quest

'Department of Work and Pensions (DWP)', Longbenton, Newcastle.'On Line Services' Account, Camberly, Surrey.'LTSB Central Lending Platform' Account, Camberly, Surrey

ComponentSource (www.componentsource.com) 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