Senior Test Analyst - ISTQB - Job in Salford, £28,000.​00 - 30,000.​00

About the Job

To provide system test support to IT releases and projects across the Group. Accepts responsibility for creation of test cases using own in-depth technical analysis of both functional and non-functional specifications (such as reliability, efficiency, usability, maintainability and portability). Creates traceability records, from test cases back to requirements. Produces test scripts to test new and amended software or services. Specifies requirements for environment, data, resources and tools. Interprets, executes and documents complex test scripts using agreed methods and standards. Records and analyses actions and results, and maintains a defect register. Reviews test results and modifies tests if necessary. Provides reports on progress, anomalies, risks and issues associated with the overall project. Reports on system quality and collects metrics on test cases. Provides specialist advice to support others.
 
Responsibilities:
  • Perform a Test Lead role on a wide range of projects covering integration, enhancements to existing systems / applications, infrastructure / capacity upgrades and the implementation of new systems / applications.
  •  Document and enforce formal testing processes.
  • Produce following deliverables to stakeholders for each project:
Test Plan
-     Test case workbook
-     Execution plan/schedule
-     Regular progress/defect reports
-     Test completion report
-     Metrics (execution statistics to aid planning for future releases)
 
  •  Ensure relevant testing deliverables are agreed and formal sign off is obtained.
  • Interpret and analyse requirements to produce test specifications and designs and undertake test execution to ensure all software is tested to a high degree.
  • Engage with stakeholders and project management
  • Manage progress/defect review meetings (frequency dependant on project and phase) to highlight actual test progress against planned and also ensure defects are progressed through to resolution/implementation.
  •  Ensure that all issues are reported and dealt with in a timely fashion
  •  Mentor junior member of the team

 
Key Competencies & Behaviours:
  •  Leads by example demonstrating proactive approach and disseminates key technical information to team expanding their knowledge and awareness of test procedures
  •   Plans, schedules and sets own deadlines for delivery and keeps the business updated of progress
  •   Continually strives for personal improvement and seeks regular feedback on performance
  •   Has an appreciation of the wider field of information systems and impact of own work on system deployments
  •   Comfortable operating in a dynamic, fluid environment and applies a degree of flexibility to own working arrangements when required
  • Represents the department and encourages constructive feedback in managing customers’ expectations and considers  areas for improvement
  •   Applies analytical approach to test processes and works in a structured and logical way
  •   Ability to write and maintain clear and concise documentation for all test procedures.
  •   Applies rigour and challenge in providing robust testing processes
  •   Articulate and able to discuss ideas and improvements with both technical and non-technical audiences; concise, efficient and professional in the delivery of all verbal or written communication.
  • Demonstrates the ability to understand and interpret business information
Apply: here

Comments

  1. Supreme2u27 November 2013 at 14:06

    I got those skills definitely applying!

    ReplyDelete
    Replies
    1. Anonymous27 November 2013 at 14:06

      Yh me too mate my ISTQB is coming in handy now lol

      Delete

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components ...
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component  ...
Read more