Common Software Testing Terms:

General Testing Terms

• Functional Testing: function is to help in ensuring smooth performance of all the major functions.
• Non Functional Testing: function is to help in assuring the reliability and security of the application.

Computer Terms

• Mainframe: high performance computers with large amounts of memory and processors that process billions of simple calculations and transactions in real time. They are critical to databases, transaction servers, and applications that required high reliability, scalability, compatibility, and security. Mainframe testing

Database Terms

• Database Management System (DBMS) : is system software for creating and managing databases. A DBMS makes it possible for end users to create, read, update and delete data in a database. The DBMS essentially serves as an interface between databases and end users or application programs, ensuring that data is consistently organized and remains easily accessible.
• Non-Relational Databases : these databases are typically more scalable and flexible than Relational Databases. Examples : Apache HBase, IBM Domino, and Oracle NoSQL db.
• Relational Databases : is a set of formally described tables from which data can be accessed or reassembled in many different ways without having to reorganize the database tables. The standard user and application programming interface (API) of a relational database is the Structured Query Language (SQL). SQL statements are used both for interactive queries for information from a relational database and for gathering data for reports. (Rows and Columns structure)
• Structured Query Language (SQL) : is a standard DB language which is used to create, maintain, and retrieve the Relational Database. SQL is the programming language for relational databases. Examples : MySQL , Oracle, Sybase, SQL Server, DB2, Postgre, etc. Other non-relational databases (also called NoSQL ): MongoDB , DynamoDB , others, do not use SQL

Intergration Terms

• Active - Active : consists of at least two nodes, both actively running the same kind of service simultaneously. The main purpose of an active-active cluster is to achieve load balancing. Load balancing distributes workloads across all nodes in order to prevent any single node from getting overloaded. Because there are more nodes available to serve, there will also be a marked improvement in throughput and response times. [1]
  • Let it fail, but fix it fast. This is the premise behind active - active. [2]
  • Nodes and database copies are geographically distributed. Should a disaster take out a node or a database site, there are others in the network to take its place. [2]
  • Active - Active diagram link [1]
• Active - Passive : consists of at least two nodes but not all nodes are going to be active, so one node is active all others are not active. [1]
  • The passive server serves as the Failover/Backup server and is activated if the other server goes down
  • For both types it is important that all instances of the server have exactly the same settings
  • Active - Passive diagram link [1]

Load and Performance Terms

• 90th Percentile (90%): The elapsed time below which 90% of the samples fall
• Elapsed Time : Measures the elapsed time from just before sending the request to just after the last chunk of the response has been received.
• Latency : Measures the latency from just before sending the request to just after the first chunk of response has been received. In other words the time delay between the cause and the effect of some physical change in the system being observed
• JMeter : is a 100% pure Java desktop application designed to load test functional behavior and measure performance
• Throughput : Calculated as request per unit of time. The time is calculated from the start of the first sample to the end of the last sample. The formula is: Throughput = Number of Requests/Total Time

Migration Related Terms

• Rebuild : might have to build some things on top of the current code for it to more compatible in the new environment (before migration)
• Refactor : might not be fully compatible with the new environment upon migration, have to do a bit with configuration settings or refactoring
• Rehost : already exists in old environment and is being migrated to the new environment
• Revise : Change a few things on old environment (before migration) and then move it to the new environment

Resource(s)

• [1] https://www.jscape.com/blog/active-active-vs-active-passive-high-availability-cluster
• [2] http://www.availabilitydigest.com/public_articles/0101/what_is_active-active.pdf