ATASH Enterprises

Quality Assurance

Quality Assurance: Responsible for performing tests on computer applications to isolate and solve issues. Initiates tests, analyzes result, and finds solutions to technical problems.

  • Record and document results and compare to expected results.
  • Design and executive test plans on computer applications.
  • Detect software failures so that defects may be discovered and corrected.
  • Generate historical analysis of test results.
  • Document anomalies and issues.
  • Maintain a database of software defects.
  • Examine the code and execution of code in various environments.
  • Verify specific action or function of the code.
  • Operate and maintain test networks.
  • Develop and document application test plans based on software requirements and technical specifications.
  • Create meaningful error handling procedures for application code.
  • Ensure compliance with general programming best practices, accepted web standards and those standards set forth by upstream sources.
  • Perform application security audits, reviews, walkthroughs, or inspections.
  • Implement application designs, create queries, scripts, web pages and other deliverables.
  • Ensure data integrity standards.

Desired Skills:

  • Bachelor’s degree in computer science or related technical discipline.
  • 4+ years QA experience in an IT environment.
  • 4+ years experience with formal test tools and common software quality test tools.
  • Experience with Visual Studio Team Foundation Server (TFS) / Visual Studio Test Professional and Microsoft Test Manager.
  • Experience with SDLC, Agile / Scrum and waterfall methodologies.
  • Understanding of QA processes, practices and systems.
  • Experience executing and coordinating integration, system, regression and User Acceptance Testing (UAT).
  • Demonstrated ability to work on concurrent projects, activities and tasks under time constraints, team-based environments.
  • Knowledge of supply chain and logistics, Development background a plus.
  • Experience testing applications built in Angular web application framework a plus.
  • Experience using TestComplete or Protractor Automated Regression Tools.
  • Experience performing API testing.

Preferred:

  • Microsoft Test Manager
  • Test Strategy
  • Test Plan
  • Test Case Writing
  • Bug Tracking
  • Test Metrics
  • Requirement Traceability Matrix (RTM)
  • Red-Gate Software knowledge
  • Crystal Reports
  • Beyond Compare (Comparison tool)
  • Ultra-edit (data file viewing/editing tool)

ASQ (American Society for Quality) Certification, CTQ (Certified Quality Technician), CQE (Certified Quality Engineer) preferred

INTERVIEW QUESTIONS:

Q. What is the difference between the QA and software testing?

The role of QA (Quality Assurance) is to monitor the quality of the process to produce a quality of a product. While the software testing, is the process of ensuring the final product and check the functionality of the final product and to see whether the final product meets the user’s requirement.

Q. What is a Test case?

Test case is a specific term that is used to test a specific element.  It has information of test steps, prerequisites, test environment and outputs.

Q. What are the types of documents in QA?

  • Requirement Document.
  • Test Metrics.
  • Test cases and Test plan.
  • Task distribution flow chart.
  • Transaction Mix.
  • User profiles.
  • Test log.
  • Test incident report.
  • Test summary report.

Q. Explain what should your QA documents include?

  • List the number of defects detected as per severity level.
  • Explain each requirement or business function in detail.
  • Inspection reports.
  • Configurations.
  • Test plans and test cases
  • Bug reports
  • User manuals
  • Prepare separate reports for managers and users

Q. What is Testware?

Testware is the subset of software, which helps in performing the testing of an application.  It is a term given to the combination of a software application and utilities which is required for testing a software package.

Q. When to start QA in a project?

A good time to start the QA is from the beginning of the project startup. This will lead to plan the process which will make sure that the product coming out meets the customer quality expectation. QA also plays a major role in the communication between teams. It gives time to step up the testing environment. The testing phase starts after the test plans are written, reviewed and approved.

Q. What is the difference between build and release?

Build: It is a number given to installable software that is given to the testing team by the development team.

Release: It is a number given to installable software that is handed over tothe customer by the tester or developer.

Q. What are the automation challenges that QA team faces while testing?

  • Exploitation of automation tool
  • Frequency of use of test case
  • Reusability of Automation script
  • Adaptability of test case for automation

Q. What is bug leakage and bug release?

Bug release is when software or an application is handed over to the testing team knowing that the defect is present in a release. During this, the priority and severity of the bug are low, as the bug can be removed before the final handover.

Bug leakage happens when the bug is discovered by the end users or customer, and missed by the testing team to detect, while testing the software.

Q. What is data driven testing?

Data driven testing is an automation testing part, which tests the output or input values. These values are read directly from the data files. The data files may include csv files, excel files, data pools and many more. It is performed when the values are changing by the time.

Q. Explain the steps for Bug Cycle.

  • Once the bug is identified by the tester, it is assigned to the development manager in open status.
  • If the bug is a valid defect the development team will fix it and if it is not a valid defect, the defect will be ignored and marked as rejected.
  • The next step will be to check whether it is in scope, if it is happen so that, the bug is not the part of the current release then the defects are postponed.
  • If the defect or bug is raised earlier then the tester will assign a DUPLICATE status.
  • When a bug is assigned to a developer to fix, it will be given an IN-PROGRESS status.
  • Once the defect is repaired, the status will changed to FIXED at the end the tester will give CLOSED status if it passes the final test.

Q. Mention the different types of software testing?

  • Unit testing.
  • Integration testing and regression testing.
  • Shakeout testing.
  • Smoke testing.
  • Functional testing.
  • Performance testing.
  • White box and Black box testing.
  • Alpha and Beta testing.
  • Load testing and stress testing.
  • System testing.

Q. What are the contents in test plans and test cases?

  • Testing objectives.
  • Testing scope.
  • Testing the frame.
  • The environment.
  • Reason for testing.
  • The criteria for entrance and exit.
  • Deliverables.
  • Risk factors.

Q. What is agile testing and what is the importance of Agile testing?

Agile testing is software testing, which involves the testing of the software from the customer point of view.  The importance of this testing is that, unlike the normal testing process, this testing does not wait for the development team to complete the coding first and then doing testing. The coding and testing both goes simultaneously.  It requires continuous customer interaction.

It works on SDLC methodologies, it means that the task is divided into different segments and compiled at the end of the task.