Tester

DESCRIPTION OF THE TASKS

Following tasks will be performed by external service provider:

Task 1 – Definition of tests scenarios and test cases

The general purpose of "Task 1 - Tests scenarios and test cases" is to define accurately the test perimeter. Within the whole work programme, such task will focus on releasing the test scenario(s) and the test cases.

These artefacts are an important part of the test campaign. When provided by the Contractor, the test scenarios and test cases have to be derived from the functional and non-functional documentation provided by the concerned project manager, as well from direct interviews to the final users.

The concerned project manager has to approve the coverage rate of the requirements by the test cases proposed by the Contractor.

The test cases have to be classified according to the types provided below, depending on the test purpose. Other specifications (namely, the objective of the tests, the tests strategy etc.) will be agreed by the concerned project manager with the Contractor and precisely finalized in the specific test management plan.

• Functional tests: they focus on any requirements for test that can be traced directly to use cases or business functions and business rules. The goals of these tests are to verify proper data acceptance, processing, and retrieval, and the appropriate implementation of the business rules. This type of testing is based upon black box techniques; that are verifying the application and its internal processes by interacting with the application via the User Interface (UI) and analysing the output or results.

• User Interface (UI) tests: they verify a user's interaction with the software. The goal of UI Testing is to ensure that the User Interface provides the user with the appropriate access and navigation through the functions of the application.

• Regression tests: re-testing of a previously tested program following modification, to ensure that faults have not been introduced or uncovered as a result of the changes made. Regression tests are mandatory when a patch is released.

• Performance tests: they measure response times, transaction rates, and other time sensitive requirements. The goal of the Performance tests is to verify and validate the performance requirements have been achieved. Performance tests have to be usually executed several times, each using a different "background load" on the system.

• Security tests: they are performed on an application-level, with the goal to verify that user can access only those functions / data for which their user type is provided permissions.

• Volume tests: they subject the software to large amounts of data to determine if limits are reached that cause the software to fail. Volume testing also identifies the continuous maximum load or volume the system can handle for a given period.

Expected deliverables are:

• A full set of test scenarios and test cases addressing the Test management Plan.

• Automated execution of the test scenarios and test cases where applicable

Task 2: Test management plan

The general purpose of the task 2 is to provide a planning artefact to the test session. Within the whole work programme, this task will focus on producing the test management plan.

The test management plan must be approved by the concerned EC project manager before the tests execution phase. The test management plan must provide, at least, the following information:

• • The extent of the specific testing campaign and the target test items;
• • A list of test scenarios with references to test cases to be created.
• • Role-Responsibility matrix and, when needed, staffing;
• • The type of tests to be performed (see list at par. 4.1) and, for each type, details about the test objective, the test technique that will be used, the reference documentation (use cases, requirements, etc.), the completion criteria and the preconditions for testing;
• • Planning information: time schedule of the test sessions by test type; delivery dates of the test deliverables.

• • Information about the test environment: quantity and system configuration of the workstations to be used, browsers brand and version, additional environments needed to run the client (i.e. local database installed, Java RE, web application server, etc.);
• • The test strategy: fail/pass criteria;
• • Entry and exit criteria: activities that must be completed before the execution of the test management plan, and activities that must be finished in order to complete the test management plan;
• • Specific criteria for suspend/resume the tests according to the severity of the issues found;
• • Risks plan with information about risk severity, mitigation strategy, risk owner;
• • The minimal list of the artefacts to be provided is:
• – A test evaluation summary: test coverage and test results for each test case;
• – Incident log in CITNET Jira for failed tests or discovered issues;
• – For regression tests: logs from scripts execution, results of the check clearly specifying whether the program behaviour has changed and whether previously fixed faults have re-emerged.

3. LEVEL OF EDUCATION

As stated in the Article 2.6.3.1. of DIGIT-TM II Service requirements, a minimum educational qualification for lot 2 is: Level of education corresponding to Level 6 of the European Qualification Framework which typically corresponds to a bachelor degree of 3 years.

KNOWLEDGE AND SKILLS

Following skills and knowledge are required for the performance of the above listed tasks:

• Very good knowledge of

• Atlassian product family for

• Tracking & support -> JIRA

• Collaboration -> Confluence

• Deployment -> Bitbucket & Bamboo

• Web Application servers: WebLogic, Tomcat, IIS

• Database system Oracle RDBMS and database programming language PL/SQL

KNOWLEDGE AND SKILLS

Following skills and knowledge are required for the performance of the above listed tasks:

• Good knowledge of • Data representing languages such as XML / JSON

• Webservices for data / information exchange between applications based on SOAP / REST

• Windows and Linux operation systems

• Test automation tools: SOAPUI, POSTMAN

• Ability to analyse user requirements and design / implement appropriate solutions

• Very good analytical skills for problem solving

• Ability to apply high quality standards

• Capability to write clear and structured technical documents and preparation of written reports

• Ability to cope with fast changing technologies used application developments and testing

• Very good communication skills with technical and non-technical audiences

• Ability to participate in technical meetings and good communication skills

• Capability of integration in an international/multi-cultural environment, rapid self-starting capability and experience in working in team.

5. SPECIFIC EXPERTISE

Following specific expertise1 is mandatory for the performance of tasks:

• At least 2 years of specific expertise as API and Web testing

• At least 3 year of experience working with XML/JSON for structured information exchange (min. competence level 3)2

• At least 3 years of experience working with test automation technologies, tools and techniques solutions and defect tracking tools (min. competence level 3)3

• At least 3 years of specific expertise in the creation of test automation solutions (min. competence