My QA Internship Word List

tags: Internship, QA

A compilation of essential vocabulary gathered during my internship at Rakuten, with a sum of 167.

Travel

Word count: 7

• Racco: Allow employees to reserve accommodations for business trips, with the associated fees being covered by their respective companies.
• Balloon: Incorporating JR into current platform.
• Current Platform: Japanese one
• Domestic Hotel (DH): Hotels within japan
• Dynamic Package (DP): Typically refers to a bundled offering that includes both hotel accommodation and flights.
• Overseas Hotel (OH)
• Overseas Airline (OA)

Jira

Word count: 10

• Jira: A popular project management and issue tracking tool.
• Issue: A task, bug, or feature request tracked in Jira.
• Issue Type: The kind of work being tracked (e.g., Bug, Task, Story).
• Epic: A large body of work that can be broken down into smaller tasks.
• Sprint: A time-boxed iteration of work in an Agile development process.
• User Story: A small, self-contained piece of work that delivers value to end users.
• Backlog: A prioritized list of work that needs to be done, typically stored in the project.
• Workflow: The defined set of statuses and transitions that an issue moves through during its lifecycle.
• Scrum: An Agile framework for managing and organizing work in a collaborative manner.
• Kanban: An Agile methodology focused on visualizing work, limiting work in progress, and maximizing flow.

Test-related

Word count: 21

• Defect: A flaw in the system that can cause it to produce incorrect or unexpected results.
• Regression Testing: Ensuring that new code changes do not adversely affect existing functionalities by re-executing previously conducted tests.
• Regression Testing Suite: A collection of test cases used to ensure that new changes do not adversely affect existing functionality.
• Smoke Testing: A basic test to check if essential functions work, indicating whether more comprehensive testing is warranted.
• Black Box Testing: Testing the functionality of a system without knowledge of its internal code, focusing on inputs and outputs.
• White Box Testing: Testing the internal logic and structure of a system with knowledge of its code.
• Functional Testing: Validating that a software application's features and functionalities work as intended, confirming it meets specified requirements.
• Non-Functional Testing
• Load Testing: Assessing system performance under expected and peak loads to identify bottlenecks and ensure capacity requirements.
• Automation Testing: Using specialized tools to execute tests and compare actual outcomes with expected outcomes.
• Boundary Testing: Testing the application at the boundaries of valid and invalid input values.
• Performance Testing: Evaluating software speed, responsiveness, and stability for optimal functionality.
• Usability Testing: Evaluating the user-friendliness and effectiveness of a software product by observing real users interacting with it to identify any usability issues or areas for improvement.
• Monkey Test: Random or automated inputs are applied to a program to discover unexpected behaviors or vulnerabilities.
• UAT - User Acceptance Testing: The final phase of software testing where end-users evaluate the system to ensure it meets their requirements and is ready for production.
• Acceptance Criteria: Conditions that a software application must satisfy to be accepted by a user or customer.
• Exploratory Testing: Informal testing where testers actively explore the application, design test cases, and execute them simultaneously.
• Security Testing: Evaluating a system's ability to protect data and maintain functionality under unauthorized access.
• Scalability Testing: Assessing a system's capability to handle an increasing amount of workload or data.
• End-to-End Testing: A type of software testing that validates the entire application workflow from start to finish.
• Risk-Based Testing: A testing approach that prioritizes test cases based on the perceived risks associated with different features or components of the software.

Automation Testing

Word count: 13

• Selenium: A widely used open-source tool for automating web browsers.
• Appium: An open-source tool for automating native, mobile web, and hybrid applications on iOS and Android platforms.
• TestRail: A test case management tool that allows teams to organize, track, and manage software testing efforts.
• Cypress: An end-to-end testing framework designed for modern web applications.
• Test Harness: A collection of software and test data that is configured to test a program unit by running it under varying conditions.
• Jenkins: An open-source automation server used to automate various tasks, including building, testing, and deploying software.
• TestNG: A testing framework inspired by JUnit and NUnit, with additional features such as support for annotations, data-driven testing, and parallel execution.
• Robot Framework: A generic open-source automation framework for acceptance testing, acceptance test-driven development (ATDD), and robotic process automation (RPA).
• Postman: A collaboration platform for API development, allowing users to design, mock, debug, test, document, and monitor APIs.
• Katalon Studio: A comprehensive test automation tool for web, API, mobile, and desktop application testing.
• Protractor: An end-to-end test framework for Angular and AngularJS applications, built on top of WebDriverJS.
• TestComplete: A functional testing platform for web, mobile, and desktop applications, supporting various scripting languages such as JavaScript, Python, and VBScript.
• Apache JMeter: An open-source load testing tool designed to analyze and measure the performance of web applications.

PractiTest

Word count: 8

• Test Case: Defined conditions and steps to verify system requirements, including input and expected output.
• Test Set: A collection or grouping of related test cases designed for a specific purpose or to test a particular aspect of software functionality.
• Test Instance: A specific execution of a test case with unique inputs, validating the system under those conditions.
• Test Suite: A collection of test cases or test sets grouped together for execution, often focusing on a specific feature, module, or aspect of the software.
• Test Cycle: A predefined period during which testing activities are conducted, typically aligned with the software development lifecycle or release schedule.
• Test Step: A specific action or instruction within a test case, detailing the sequence of actions to be performed during test execution.
• Traceability Matrix: A document or tool used to track the relationship between requirements, test cases, and defects to ensure comprehensive test coverage.
• Test Case Design: The process of creating and structuring test cases to effectively validate software functionality, often involving techniques such as boundary analysis, equivalence partitioning, and state transition testing.

General

Word count: 32

• PRD - Product Requirements Document: A detailed document specifying the features, functionalities, and constraints of a software product.
• BDD - Behavior Driven Development: An agile software development methodology that encourages collaboration between developers, QA, and non-technical or business participants in a software project.
• TDD - Test Driven Development: A development process that relies on the repetition of short development cycles where testing is done first.
• CI/CD - Continuous Integration/Continuous Delivery: Practices that automate the integration of code changes and ensure that software is always in a releasable state.
• Canonical: Refers to the preferred version of a URL, chosen to avoid duplicate content and enhance search engine optimization.
• Drupal: An open-source content management system (CMS) and web application framework, written in PHP. Similar to Ruby on Rails, but with a PHP foundation.
• Akamai: A cloud services provider that operates a content delivery network (CDN) to optimize the delivery of web content, streaming media, and other online services.
• Cron job: A time-based scheduler in Unix-like operating systems that automates the execution of specific commands or scripts at predetermined intervals.
• Batch: Typically refers to the automated processing of a set of tasks or data, often scheduled to run at specific intervals or triggered by specific events, such as in the context of a cron job.
• Jennifer: Jennifer is a solution that monitors web services, detects issues, provides detailed information, and automatically notifies responsible personnel via email or SMS.
• Code Review: The systematic examination of source code by developers to find and fix errors.
• API Application Programming Interface: A set of rules and tools for building software applications, allowing them to communicate with each other.
• SDK - Software Development Kit: A collection of tools, libraries, and documentation for developing software applications for a specific platform or framework.
• DevOps: A set of practices that combines software development (Dev) and IT operations (Ops) to enhance collaboration and efficiency.
• Backlog Refinement: The process of reviewing, updating, and prioritizing items in the product backlog.
• Hackathon: An event where programmers collaborate intensively on software projects within a short timeframe.
• Version Control: The management of changes to documents, computer programs, and other collections of information.
• Technical Debt: The concept in software development where shortcuts or less-than-optimal solutions are accepted to expedite delivery, leading to increased effort needed in the future.
• Docker: A platform for developing, shipping, and running applications in containers.
• Codebase: The complete set of all source code used to build an executable software application.
• Refactoring: The process of restructuring existing computer code without changing its external behavior.
• Pair Programming: An agile software development technique where two programmers work together at one workstation.
• Technical Stack: The combination of programming languages, tools, and technologies used to develop a software application.
• IDE - Integrated Development Environment: A software application providing comprehensive facilities to programmers for software development.
• Polymorphism: The ability of an object to take on different forms or behaviors based on its context or the type of reference used to access it.
• Encapsulation: The practice of bundling data and methods together in a class and controlling access to them through modifiers (e.g., private, public).
• Inheritance: The mechanism by which one class inherits properties and behaviors from another class, establishing a parent-child relationship.
• Exception Handling: The process of catching and handling runtime errors or exceptional conditions in a controlled manner to prevent program crashes.
• Garbage Collection: The automatic memory management feature in Java that deallocates memory occupied by objects that are no longer in use.
• Thread: A lightweight unit of execution within a program, allowing multiple tasks to be executed concurrently.

Project Management

Word count: 10

• MD: "Man-Day" refers to one day of work by one person, often used in project management for estimating effort.
• MM: Stands for "Man-Month," measuring one person's work in a month.
• Triage: The process of quickly assessing and prioritizing reported issues or bugs based on their severity and impact.
• Gantt Chart: A visual representation of a project schedule that shows tasks, milestones, and dependencies over time.
• SWOT Analysis: An assessment technique that identifies Strengths, Weaknesses, Opportunities, and Threats related to a project.
• Project Kickoff: The initial meeting or event marking the start of a project.
• Stakeholder: Any individual or group that has a vested interest or "stake" in the success of the project.
• User Persona: A detailed and semi-fictional representation of your ideal customer based on market research and real data.
• Agile Manifesto: A set of guiding values and principles for Agile software development.
• Scrum Master: A role in Scrum responsible for facilitating and ensuring the Scrum team follows agile principles and practices.

Cloud Computing

Word count: 5

• AWS - Amazon Web Services: A comprehensive, evolving cloud computing platform provided by Amazon.
• Azure: Microsoft's cloud computing service, offering a variety of services, including virtual computing and analytics.
• Google Cloud Platform (GCP): A suite of cloud computing services provided by Google.
• SaaS - Software as a Service: A software distribution model where applications are hosted by a third-party provider and made available to customers over the internet.
• IaaS - Infrastructure as a Service: A cloud computing model where virtualized computing resources are offered over the internet.

DevOps Tools

Word count: 3

• GitLab CI/CD: A continuous integration and continuous delivery platform integrated with GitLab.
• Kubernetes: An open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications.
• Terraform: An open-source infrastructure as code software tool that provides a consistent CLI (Command Line Interface) workflow to manage hundreds of cloud services.

DS/ DA/ BI

Word count: 10

• Machine Learning: A subset of artificial intelligence that focuses on the development of algorithms enabling computers to learn patterns and make decisions.
• Data Wrangling: The process of cleaning, structuring, and enriching raw data into a desired format for better decision making in less time.
• Jupyter Notebook: An open-source web application that allows you to create and share documents that contain live code, equations, visualizations, and narrative text.
• Regression Analysis: A statistical method used to examine the relationship between one dependent variable and one or more independent variables.
• Big Data: Extremely large datasets that may be analyzed computationally to reveal patterns, trends, and associations.
• Cross-Validation: A technique to assess the performance and generalizability of a machine learning model by splitting the dataset into multiple subsets for training and testing.
• Time Series Analysis: Statistical techniques to analyze time-ordered data points.
• Business Intelligence (BI): Technologies, applications, and practices for collecting, integrating, analyzing, and presenting business information.
• Natural Language Processing (NLP): A field of study focused on enabling computers to understand, interpret, and generate human language data.
• Data Warehouse: A central repository of integrated data from one or more disparate sources, used for reporting and analysis.

Java

Word count: 10

• Java: A popular programming language known for its platform independence and object-oriented features.
• JDK: Java Development Kit, a set of tools and libraries used for developing Java applications.
• JVM: Java Virtual Machine, the runtime environment that executes Java bytecode.
• Class: A blueprint or template for creating objects in Java.
• Object: An instance of a class that encapsulates data and behavior.
• Maven: A build automation and dependency management tool used primarily for Java projects.
• POM: Project Object Model, an XML file that contains information about a Maven project's configuration, dependencies, and build settings.
• Geckodriver: A proxy for using the Gecko-based web browser engines (like Firefox) with Selenium WebDriver.
• Chromedriver: A standalone server that enables communication between Selenium WebDriver and the Chrome browser.
• JUnit: A popular Java framework for writing and running unit tests.

Ruby

Word count: 25

• Ruby: A dynamic, open-source programming language known for its simplicity and productivity.
• Ruby on Rails: A web application framework written in Ruby, designed to make web development easier and more efficient.
• Gem: A package or library in Ruby, used for code reuse and distribution.
• Bundle: A tool in Ruby for managing dependencies and gems within a project.
• RVM: Ruby Version Manager, a command-line tool used to manage multiple Ruby environments.
• IRB: Interactive Ruby, a command-line REPL (Read-Eval-Print Loop) for Ruby.
• RSpec: A popular Ruby testing framework used for behavior-driven development (BDD).
• Capybara: An acceptance testing framework for web applications, often used with RSpec.
• ActiveRecord: The ORM (Object-Relational Mapping) layer in Rails, providing database abstraction.
• MVC: Model-View-Controller, an architectural pattern commonly used in web applications, including Rails.
• ActionController: The controller component in Rails responsible for handling HTTP requests.
• ActionView: The view component in Rails responsible for rendering HTML templates.
• ActionMailer: The component in Rails used for sending email messages from applications.
• ActiveJob: A framework in Rails for declaring and executing background jobs.
• Devise: A flexible authentication solution for Rails applications.
• CarrierWave: A file upload solution for Rails applications.
• Paperclip: Another file upload solution for Rails, now deprecated in favor of Active Storage.
• ActiveStorage: A built-in solution for file uploads and storage in Rails applications.
• Sprockets: The asset pipeline in Rails for managing and serving static assets like JavaScript and CSS files.
• Turbolinks: A library in Rails for speeding up navigation and page loading by using AJAX.
• FactoryBot: A gem for defining and managing factories for test data in Rails applications.
• RuboCop: A Ruby static code analyzer and formatter, often used for enforcing coding style and best practices.
• Redis: An open-source, in-memory data store often used as a cache or message broker in Rails applications.
• Rack: A modular Ruby web server interface that provides a common API for web servers, frameworks, and middleware.
• Migrations: Ruby classes used to define changes to the database schema over time.

Jenkins

Word count: 13

• Pipeline: A series of automated steps that define a software delivery process.
• Job: A task or set of tasks that Jenkins executes as part of a build process.
• Plugin: A piece of software that extends the functionality of Jenkins.
• Master/Slave configuration`: A setup where one Jenkins master node controls multiple Jenkins slave nodes to distribute workload.
• Build: The process of compiling, testing, and packaging software in Jenkins.
• Trigger: Event or condition that starts a Jenkins build or job.
• Artifact: A file generated by a Jenkins build, such as a compiled binary or a test report.
• Docker integration: Integration with Docker containers to execute builds or run applications in Jenkins.
• Configuration as Code: Managing Jenkins configuration using code files, such as Jenkinsfile or YAML configurations.
• Blue Ocean: A Jenkins plugin providing a more modern and user-friendly interface for pipeline visualization and management.
• Environment Variables: Variables defined globally or per job in Jenkins, used to customize build steps or provide configuration information.
• Post-Build Action: Actions performed after a build completes, such as archiving artifacts, triggering downstream jobs, or sending notifications.
• Parameterized Build: A build in Jenkins that accepts parameters, allowing users to customize the build process when triggering it manually or via a trigger.