QA Tester – Oracle APEX, Java/JEE
Demonstrated skills and experience as a System Testing/QA Specialist application based on Oracle APEX and Java/JEE web technologies
- Experience with Oracle APEX, SQL and PL/SQL;
- Experience in system testing using Java technologies
- 10 or more years of experience as a Systems Testing/QA Specialist
- Demonstrated experience in all functions of system testing involving Java and Oracle database technologies;
- Demonstrated knowledge and understanding of testing methods in an object-oriented environment;
- Demonstrated experience in understanding and use of OLTP data model based database;
- Ability to identify, trace, isolate and replicate problems and successfully conduct root cause analysis as required;
- Experience in reviewing system requirements in ensuring the QA Test Cases are adequately covered;
- Experience in documenting in detail the QA Test Cases, and other related QA artifacts;
- Experienced with using defect management tools for QA/QC work (e.g. Rational Team Concert (RTC), Rational Quality Manager (RQM) or similar tools);
- Experience in managing defect reporting and resolution during the defect cycle, this includes working with the user acceptance test lead to report and resolve defects in a timely manner;
- Experience with SQL tools required in working the Oracle database;
- Demonstrated experience in development of test plan and reusable test cases; and
- Excellent analytical and interpersonal skills; excellent English language verbal and written communication skills.
- Experience in contributing to large, complex, IT system development and implementation projects;
- A team player with a track record for meeting deadlines;
- Experience in the development of distributed applications; and
- Experience with projects of a similar nature.
- Participate in requirement review and walkthrough meetings;
- Provide estimate on test effort based on requirements and constraints;
- Review test schedule;
- Prepare and document test plans, test scenarios, test cases and test data using Rational Quality Manager;
- Assist in readiness of test environment for testing;
- Examine all testing related deliverables for Code Release and determine if the artefacts are complete and correct according to Client and Cluster standards and guidelines;
- Execute and record the results for the following types of tests;
Functional testing including:
- Application integration (links, connections, security transactions between functions and main modules);
- System testing (end-to-end testing);
- Regression testing;
- Acceptance testing;
- Accessibility for Ontarians with Disabilities Act (AODA) testing (Level of Conformance Required is AA as defined in “Web Content Accessibility Guidelines (WCAG) 2.0”);
- Security testing including Application Vulnerability Testing;
- Data and database integrity testing;
- Configuration testing;
- Stress testing; and,
- Load and volume testing.
- Record application defects reported in the Cluster’s defect reporting tool – Rational Team Concert, provide review, update; and retest of defect upon resolution;
- Coordinate and facilitate regular defect review meeting;
- Provide defect status reports throughout the testing cycles;
- Confirm production readiness of infrastructure and web based applications and Code Releases;
- Assist business users in user acceptance testing;
- Notify the IT Development Lead of issues;
- Participate in regular project team meeting and provide status and update as required;
- Provide weekly report confirming status of assigned tasks;
- Review, create and modify scripts for automatic testing using Rational Functional Tester;
- Test new Code Releases and infrastructure hardware and software following Cluster test cases procedures;
- Review QA related application documentations;
- Troubleshoot and test Java and Oracle APEX and ETL systems;
- Troubleshoot and test infrastructure hardware and software.
- Prioritize problems based on severity level definitions;
- Identify problems, isolate them and document as defect;
- Regression test for resolved defects
Functional testing includes the following:
1. Component level testing;
2. Low level (test cases, GUI, check lists);
3. Functional (test existing functions, sub-functions and their objects);
4. Non-functional (boundary conditions- “login” and “password” windows, security issues); and,
5. Reusable automated test script development for automated regression testing.
- Data and Database Integrity Testing - The databases and the database processes should be tested as separate systems within the test plan. These systems should be tested without the application (as the interface to the data).
- System Testing - System testing should focus on any target requirements 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.
- Load Testing - Load testing measures subject the system-under-test to varying workloads to evaluate the systems ability to continue to function properly under these different workloads. The goal of load testing is to determine and ensure that the system functions properly beyond the expected maximum workload. Additionally, load testing evaluates the performance characteristics (response times, transaction rates, and other time sensitive issues).
- Stress Testing - Stress testing is intended to find errors due to low resources or competition for resources. Low memory or disk space may reveal defects in the software that aren't apparent under normal conditions. Other defects might result from competition for shared resources like database locks or network bandwidth. Stress testing identifies the peak load the system can handle.
- Security and Access Control Testing -Security and access control testing focus on two key areas of security:
- Application security, including access to the data or business functions, and system security, including logging into / remote access to the application
- Application security which ensures that, based upon the desired security, users are restricted to specific functions or are limited in the data that is available to them. For example, everyone may be permitted to enter data and create new accounts, but only managers can delete them. If there is security at the data level, testing ensures that ‘user “type” one’ can see all customer information, including financial data, however, ‘user “type” two’ only sees the demographic data for the same ministry. System security ensures that only those users granted access to the system are capable of accessing the application and only through the appropriate gateways.
- Configuration Testing - Configuration testing verifies operation of the software on different software and hardware configurations. In most production environments, the particular hardware specifications for the Client workstations, network connections and database servers vary. Client workstations may have different software loaded (e.g. applications, drivers, etc.) and at any one time many different combinations may be active and using different resources.