*Job Title:*

*QA Automated Test Lead Location: NYC (midtown) Duration: 6 months*


*Visa: **USC, GC, or EAD (GC, H4)*


·         The QE Lead / Principal Quality Engineer will be responsible for
the strategy, assessment, and automation testing priorities to ensure the
best quality results for the eCMS (electronic Content Management Systems)
program.

·         The QE Lead to design, create and maintain automated test scripts
that will be used to validate the quality of software applications.

·         With guidance from Quality leadership, the QA Lead will drive the
test strategy for validating new applications, or changes to existing
applications.

*The QE Lead will:*

·         collaborate closely with engineers, business analysts and product
owners and other team members to determine appropriate acceptance criteria
for all changes (new features as well as updates)

·         be responsible to review unit test coverage implemented by
engineers so as to inform QE test strategy

·         be responsible to design and implement automated test harnesses
and tests based on the agreed-upon acceptance criteria. The QE Lead may
work with other automated test engineers for this

·         be responsible to setup the execution of automated tests as
needed, via Continuous Integration (CI) tools

·         be responsible to review the results of automated tests and take
appropriate action (e.g. file defects, update test code/data/configuration
etc.)

·         be responsible to ensure that any areas not covered by automated
tests are validated via alternate mechanisms

·         be responsible for generating and communicating test reports and
metrics out to stakeholders

·         mentor other junior members of the team

*Essential Job Responsibilities/Primary Activities:*

·         Analytical competence, which supports Test creation

o    Proven experience testing Java applications and Web Services

o    Active Participation in determining acceptance criteria of new
features as well as changes

o    Determine appropriate test strategy for changes

o    Determine impact to test suite – need for new tests, maintenance to
current tests etc.

o    Determine test data requirements for new tests

·         Technical competence, which supports Test Implementation and eCMS

o    Experience with Acceptance Driven Development (ATDD) or Behavior
Driven Development (BDD) approaches to developing and testing software

o    Experience with Cucumber/Gherkin language to specify scenarios, or
alternate tools in the same space such as Behat, Watir etc.

o    High level of expertise with Java programming as applied to
implementing automated tests with REST services, Selenium, Databases etc.

o    Familiar with relational databases (e.g. Oracle, MySQL etc.), as well
as NoSQL databases (e.g. MongoDB, Cassandra etc.)

o    Familiar with modern version control systems such as Git, BitBucket or
similar

o    Familiar with leveraging Continuous Integration tools such as Jenkins
to setup tests to execute on schedule, on demand or true CI (e.g. chained
to code commits)

o    Familiar with using tools such as SumoLogic, Loggly or other logging
tools to correlate defects against other events of interest

o    Familiar with Fiddler, Charles, Postman, REST-Client, SOAP UI or
similar tools to independently test REST end points to correlate and
isolate defect causes

o    Able to review code changes at a high level, understand unit test
coverage and design automated tests that complement developer unit tests

o    Experience with Open Text Media Manager, or other similar eCMS tools a
plus

·         Other competence, which supports Quality

o    Strong adherent to Agile principles in letter as well as in spirit.
Knows and follows Agile convention, but importantly internalizes the Agile
spirit

o    Strong communicator – able to work closely with counterparts in a
cross-functional, Agile team setting, to understand product needs and
implement the right automated tests

o    Understands the importance of data insofar as to analyze reported
issues, inform severity of defects, inform the priority of tests

o    Understands the importance of metrics in the modern software
organization and supports the automated generation of such metrics as an
outcome of normal work. Observes patterns in the metrics and takes
appropriate action

o    Understands the importance of performance of software and is able to
interface with performance test teams to highlight and resolve performance
problems in applications



*Thanks & Regards,*

*Abhishek Ojha*

*732- 837- 2138*

*ao...@sagetl.com <ao...@sagetl.com>*

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-developers+unsubscr...@googlegroups.com.
To post to this group, send email to android-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/CAKpcopSdY8giP4-iSgqXgZqXbu7bOA71ZgTop-%2Bt%2BrY2YoN8bQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to