#portability testing

[redactedconcepts]

Never forget a test

Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not. Testing is executing a system in order to identify any gaps, errors, or missing requirements contrary to the actual requirements. This tutorial will give you a basic understanding of software testing, its types, methods, levels, and other related terminologies.

Code that is not tested can’t be trusted

Bad reputation

“Testing is Too Expensive”: Pay less for testing during software development => pay more for maintenance or correction later. Early testing saves both time and cost in many aspects. However, reducing the cost without testing may result in improper design of a software application, rendering the product useless.

“Testing is Time-Consuming”: Testing is never a time-consuming process. However diagnosing and fixing the errors identified during proper testing is a time-consuming but productive activity.

“Only Fully Developed Products are Tested”: No doubt, testing depends on the source code but reviewing requirements and developing test cases is independent from the developed code. However, iterative or incremental approaches to a development life cycle model may reduce the requirement of testing on the fully developed software.

“Complete Testing is Possible”: It becomes an issue when a client or tester thinks that complete testing is possible. It is possible that all paths have been tested by the team but occurrence of complete testing is never possible. There might be some scenarios that are never executed by the test team or the client during the software development life cycle and may be executed once the project has been deployed.

“A Tested Software is Bug-Free”: No one can claim with absolute certainty that a software application is 100% bug-free even if a tester with superb testing skills has tested the application.

“Testers are Responsible for Quality of Product”: It is a very common misinterpretation that only testers or the testing team should be responsible for product quality. Testers’ responsibilities include the identification of bugs to the stakeholders and then it is their decision whether they will fix the bug or release the software. Releasing the software at the time puts more pressure on the testers, as they will be blamed for any error.

“Test Automation should be used wherever possible to Reduce Time”: Yes, it is true that Test Automation reduces the testing time, but it is not possible to start test automation at any time during software development. Test automaton should be started when the software has been manually tested and is stable to some extent. Moreover, test automation can never be used if requirements keep changing.

Basic

This standard deals with the following aspects to determine the quality of a software application:

Quality model

External metrics

Internal metrics

Quality in use metrics

This standard presents some set of quality attributes for any software such as:

Functionality

Reliability

Usability

Efficiency

Maintainability

Portability

Functional Testing

This is a type of black-box testing that is based on the specifications of the software that is to be tested. The application is tested by providing input and then the results are examined that need to conform to the functionality it was intended for. Functional testing of a software is conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements.

There are five steps that are involved while testing an application for functionality:

The determination of the functionality that the intended application is meant to perform.

The creation of test data based on the specifications of the application.

The output based on the test data and the specifications of the application.

The writing of test scenarios and the execution of test cases.

The comparison of actual and expected results based on the executed test cases.

An effective testing practice will see the above steps applied to the testing policies of every organization and hence it will make sure that the organization maintains the strictest of standards when it comes to software quality.

Unit Testing

This type of testing is performed by developers before the setup is handed over to the testing team to formally execute the test cases. Unit testing is performed by the respective developers on the individual units of source code assigned areas. The developers use test data that is different from the test data of the quality assurance team.

The goal of unit testing is to isolate each part of the program and show that individual parts are correct in terms of requirements and functionality.

Limitations of Unit Testing:

Testing cannot catch each and every bug in an application. It is impossible to evaluate every execution path in every software application. The same is the case with unit testing.

There is a limit to the number of scenarios and test data that a developer can use to verify a source code. After having exhausted all the options, there is no choice but to stop unit testing and merge the code segment with other units.

Integration Testing

Integration testing is defined as the testing of combined parts of an application to determine if they function correctly. Integration testing can be done in two ways: Bottom-up integration testing and Top-down integration testing.

Bottom-up integration: This testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds.

Top-down integration: In this testing, the highest-level modules are tested first and progressively, lower-level modules are tested thereafter.

In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. The process concludes with multiple tests of the complete application, preferably in scenarios designed to mimic actual situations.

System Testing

System testing tests the system as a whole. Once all the components are integrated, the application as a whole is tested rigorously to see that it meets the specified Quality Standards. This type of testing is performed by a specialized testing team.

System testing is important because of the following reasons:

System testing is the first step in the Software Development Life Cycle, where the application is tested as a whole.

The application is tested thoroughly to verify that it meets the functional and technical specifications.

The application is tested in an environment that is very close to the production environment where the application will be deployed.

System testing enables us to test, verify, and validate both the business requirements as well as the application architecture.

Regression Testing

Whenever a change in a software application is made, it is quite possible that other areas within the application have been affected by this change. Regression testing is performed to verify that a fixed bug hasn’t resulted in another functionality or business rule violation. The intent of regression testing is to ensure that a change, such as a bug fix should not result in another fault being uncovered in the application.

Regression testing is important because of the following reasons:

Minimize the gaps in testing when an application with changes made has to be tested.

Testing the new changes to verify that the changes made did not affect any other area of the application.

Mitigates risks when regression testing is performed on the application.

Test coverage is increased without compromising timelines.

Increase speed to market the product.

Acceptance Testing

This is arguably the most important type of testing, as it is conducted by the Quality Assurance Team who will gauge whether the application meets the intended specifications and satisfies the client’s requirement. The QA team will have a set of pre-written scenarios and test cases that will be used to test the application.

More ideas will be shared about the application and more tests can be performed on it to gauge its accuracy and the reasons why the project was initiated. Acceptance tests are not only intended to point out simple spelling mistakes, cosmetic errors, or interface gaps, but also to point out any bugs in the application that will result in system crashes or major errors in the application.

By performing acceptance tests on an application, the testing team will deduce how the application will perform in production. There are also legal and contractual requirements for acceptance of the system.

Alpha Testing

This test is the first stage of testing and will be performed amongst the teams (developer and QA teams). Unit testing, integration testing and system testing when combined together is known as alpha testing. During this phase, the following aspects will be tested in the application:

Spelling Mistakes

Broken Links

Cloudy Directions

The Application will be tested on machines with the lowest specification to test loading times and any latency problems.

Beta Testing

This test is performed after alpha testing has been successfully performed. In beta testing, a sample of the intended audience tests the application. Beta testing is also known as pre-release testing. Beta test versions of software are ideally distributed to a wide audience on the Web, partly to give the program a “real-world” test and partly to provide a preview of the next release. In this phase, the audience will be testing the following:

Users will install, run the application and send their feedback to the project team.

Typographical errors, confusing application flow, and even crashes.

Getting the feedback, the project team can fix the problems before releasing the software to the actual users.

The more issues you fix that solve real user problems, the higher the quality of your application will be.

Having a higher-quality application when you release it to the general public will increase customer satisfaction.

Non-Functional Testing

This section is based upon testing an application from its non-functional attributes. Non-functional testing involves testing a software from the requirements which are nonfunctional in nature but important such as performance, security, user interface, etc.

Some of the important and commonly used non-functional testing types are discussed below.

Performance Testing

It is mostly used to identify any bottlenecks or performance issues rather than finding bugs in a software. There are different causes that contribute in lowering the performance of a software:

Network delay

Client-side processing

Database transaction processing

Load balancing between servers

Data rendering

Performance testing is considered as one of the important and mandatory testing type in terms of the following aspects:

Speed (i.e. Response Time, data rendering and accessing)

Capacity

Stability

Scalability

Performance testing can be either qualitative or quantitative and can be divided into different sub-types such as Load testing and Stress testing.

Load Testing

It is a process of testing the behavior of a software by applying maximum load in terms of software accessing and manipulating large input data. It can be done at both normal and peak load conditions. This type of testing identifies the maximum capacity of software and its behavior at peak time.

Most of the time, load testing is performed with the help of automated tools such as Load Runner, AppLoader, IBM Rational Performance Tester, Apache JMeter, Silk Performer, Visual Studio Load Test, etc.

Virtual users (VUsers) are defined in the automated testing tool and the script is executed to verify the load testing for the software. The number of users can be increased or decreased concurrently or incrementally based upon the requirements.

Stress Testing

Stress testing includes testing the behavior of a software under abnormal conditions. For example, it may include taking away some resources or applying a load beyond the actual load limit.

The aim of stress testing is to test the software by applying the load to the system and taking over the resources used by the software to identify the breaking point. This testing can be performed by testing different scenarios such as:

Shutdown or restart of network ports randomly

Turning the database on or off

Running different processes that consume resources such as CPU, memory, server, etc.

Usability Testing

Usability testing is a black-box technique and is used to identify any error(s) and improvements in the software by observing the users through their usage and operation.

According to Nielsen, usability can be defined in terms of five factors, i.e. efficiency of use, learn-ability, memory-ability, errors/safety, and satisfaction. According to him, the usability of a product will be good and the system is usable if it possesses the above factors.

Nigel Bevan and Macleod considered that usability is the quality requirement that can be measured as the outcome of interactions with a computer system. This requirement can be fulfilled and the end-user will be satisfied if the intended goals are achieved effectively with the use of proper resources.

Molich in 2000 stated that a user-friendly system should fulfill the following five goals, i.e., easy to Learn, easy to remember, efficient to use, satisfactory to use, and easy to understand.

In addition to the different definitions of usability, there are some standards and quality models and methods that define usability in the form of attributes and sub-attributes such as ISO-9126, ISO-9241-11, ISO-13407, and IEEE std.610.12, etc.

UI vs Usability Testing

UI testing involves testing the Graphical User Interface of the Software. UI testing ensures that the GUI functions according to the requirements and tested in terms of color, alignment, size, and other properties.

On the other hand, usability testing ensures a good and user-friendly GUI that can be easily handled. UI testing can be considered as a sub-part of usability testing.

Security Testing

Security testing involves testing a software in order to identify any flaws and gaps from security and vulnerability point of view. Listed below are the main aspects that security testing should ensure:

Confidentiality

Integrity

Authentication

Availability

Authorization

Non-repudiation

Software is secure against known and unknown vulnerabilities

Software data is secure

Software is according to all security regulations

Input checking and validation

SQL insertion attacks

Injection flaws

Session management issues

Cross-site scripting attacks

Buffer overflows vulnerabilities

Directory traversal attacks

Portability Testing

Portability testing includes testing a software with the aim to ensure its reusability and that it can be moved from another software as well. Following are the strategies that can be used for portability testing:

Transferring an installed software from one computer to another.

Building executable (.exe) to run the software on different platforms.

Portability testing can be considered as one of the sub-parts of system testing, as this testing type includes overall testing of a software with respect to its usage over different environments. Computer hardware, operating systems, and browsers are the major focus of portability testing. Some of the pre-conditions for portability testing are as follows:

Software should be designed and coded, keeping in mind the portability requirements.

Unit testing has been performed on the associated components.

Integration testing has been performed.

Test environment has been established.

Test Plan

A test plan outlines the strategy that will be used to test an application, the resources that will be used, the test environment in which testing will be performed, and the limitations of the testing and the schedule of testing activities. Typically the Quality Assurance Team Lead will be responsible for writing a Test Plan.

A test plan includes the following:

Introduction to the Test Plan document

Assumptions while testing the application

List of test cases included in testing the application

List of features to be tested

What sort of approach to use while testing the software

List of deliverables that need to be tested

The resources allocated for testing the application

Any risks involved during the testing process

A schedule of tasks and milestones to be achieved

Test Scenario

It is a one line statement that notifies what area in the application will be tested. Test scenarios are used to ensure that all process flows are tested from end to end. A particular area of an application can have as little as one test scenario to a few hundred scenarios depending on the magnitude and complexity of the application.

The terms ‘test scenario’ and ‘test cases’ are used interchangeably, however a test scenario has several steps, whereas a test case has a single step. Viewed from this perspective, test scenarios are test cases, but they include several test cases and the sequence that they should be executed. Apart from this, each test is dependent on the output from the previous test.

Test Case

Test cases involve a set of steps, conditions, and inputs that can be used while performing testing tasks. The main intent of this activity is to ensure whether a software passes or fails in terms of its functionality and other aspects. There are many types of test cases such as functional, negative, error, logical test cases, physical test cases, UI test cases, etc.

Furthermore, test cases are written to keep track of the testing coverage of a software. Generally, there are no formal templates that can be used during test case writing. However, the following components are always available and included in every test case:

Test case ID

Product module

Product version

Revision history

Purpose

Assumptions

Pre-conditions

Steps

Expected outcome

Actual outcome

Post-conditions

Many test cases can be derived from a single test scenario. In addition, sometimes multiple test cases are written for a single software which are collectively known as test suites.

[adamoose-art]

Phantom cries from a child you don't remember having.

I drew @blingblandart 's isat oc, Sága, for artfight! I'll post the other attacks I've done at the end of this month, but I was especially proud of this one and wanted to show it off!

I like their style and always enjoy seeing their art on my dash so you should check out their page too!!

[minakoshoe]

The Yuki

Think he's a N.E.R.D or 50 Cent type of guy?

[cannibalisticskittles]

holiday party with the kids today so i dug out Some festive things. also crossing my fingers that the dvds i brought work alright even tho they're old as hell and i did not test them on this computer. it's fiiiiiiine.

[mapleshaiku]

Moonlight passes you

[orcelito]

My power's been out for over an hour and thankfully id already heated up my spaghettios by then but now it's been an hour and I want hot dogs now but my microwave is not an option and my stove is not an option bc I have no damn electricity

And i want hot dogs.

So now im wondering whether I could heat them up via lighter or maybe with a pan over a candle. Im getting desperate man i want hot dogs

[twistedshack]

Shoutout to my friend for encouraging me to.draw gray fox for their inspo, there's also a small william birkin I forgot to delete

[lemagdesastuces]

📱 Les codes secrets de votre smartphone que vous ne connaissiez pas ! 🔍 Saviez-vous que votre téléphone cache des fonctionnalités secrètes accessibles via des codes ? Test matériel, infos réseau, IMEI… Découvrez ces raccourcis méconnus pour maîtriser votre appareil comme un pro !

[picorimori]

My brother has been doinh the fatty fatty no parents test for 7 hours

[callmeblake]

From frankieromustdie instagram on October 2nd, 2024:

it’s been one of those weeks… 🛫🎸🎶🛬 thank you rock n roll. 😮‍💨🖤😴

He's tagged the pic of the test pressing with tags but they don't mean anything to me:

bmg_us & catbirdnyc

[gfuveelectronics]

GF312B2 PORTABLE THREE PHASE REFERENCE METER WITH CLAMP ON CT

GF312B2 portable three phase reference meter high accuracy 0.02%, with all kinds of optional clamp on ct and smart optical sampler. It can be applied in electrical laboratory or on site. it will be ensured by a combination of measures such as the use of 24bit A/D converter, DSP+32 bit ARM technology, a widely measuring range 600V/120A, adapted to typical test points of most recognized national metrological institutes. It can be as high precision three phase reference energy meter, also three phase portable meter calibrator, test ct pt ratio, burden etc.

FEATURES ■ Vector diagram function; ■ Data download by U disk; ■ With PC control software; ■ Waveform display function; ■ High accuracy up to 0.02%; ■ 7 inch TFT touch color LCD; ■ DSP+32 bit ARM technology; ■ Energy accumulating function; ■ Metal body, strong and reliable; ■ Measurement 2~63 times harmonics; ■ Suit for testing in the field or in the lab; ■ Verification of comprehensive metering device;

APPLICATION ■ Power plant; ■ Electrical laboratory; ■ Energy meter R & D; ■ Watt-hour meter factory; ■ Metrological service center; ■ Electricity power bureau & power company; ■ National Metrology and testing department; ■ Electrical Department of industrial and mining enterprises;

[this-is-turtles]

If you had one wish....what would you wish for?

Someone let this boi have a relaxing activity, he probably needs it

[theresa-of-liechtenstein]

i found out in a practice room that my fellowship application was rejected but i came across my friend (principal oboe waiting for her lesson) eating her lunch on a bench on the ground floor so i hung out with her and felt a little more human afterward so all is well

[sameeksha-4717]

Premium Visgage Oil Test Kits in India | AR Engineering

🛢️ Visgage Oil Test Kits from OilFilterMachineIndia.com offer a fast, accurate, and portable solution for monitoring oil viscosity and contamination levels. Designed for preventive maintenance, these kits help detect early signs of oil degradation in engines, turbines, compressors, and hydraulic systems.

🇮🇳 Our Visgage Oil Test Kits in India are widely used in sectors like manufacturing, marine, automotive, power plants, and heavy machinery, where regular oil condition monitoring is crucial for equipment longevity and performance.

🏭 Looking for Industrial Visgage Oil Test Kits in India? We provide durable, field-tested instruments that help measure oil viscosity against a reference standard without lab setup—ideal for plant managers and maintenance engineers.

🔧 These Oil Viscosity Test Kits in India are simple to use, lightweight, and accurate, offering on-the-spot results that reduce downtime and maintenance costs. Whether you're in remote operations or fast-paced industrial environments, our Portable Visgage Oil Test Kits in India deliver real-time insights into your lubricant condition.

🧪 Trusted by industries across the country, our Industrial Oil Testing Kits in India ensure proactive asset management. Keep your machines running efficiently with our advanced oil analysis solutions.

[new-techno]

Test Acer PD163Q : le double écran externe qui va booster votre productivité

Le télétravail et la mobilité ont transformé nos habitudes, mais une chose demeure : pour être vraiment productif, un seul écran d’ordinateur portable ne suffit souvent pas. Jongler entre les fenêtres, comparer des documents, garder un œil sur ses mails… Ces tâches deviennent vite fastidieuses. C’est ici qu’interviennent les moniteurs portables, et Acer frappe un grand coup avec son Acer PD163Q,…

[mosaic-of-light]

Good thing #104: I have the portable Blu Ray player!!! It's currently charging!!!