{"id":8517,"date":"2017-06-12T15:50:07","date_gmt":"2017-06-12T15:50:07","guid":{"rendered":"http:\/\/www.macecraft.com\/?p=8517"},"modified":"2024-07-23T06:48:30","modified_gmt":"2024-07-23T06:48:30","slug":"pc-system-utilities-software-testing-weekly-1","status":"publish","type":"post","link":"https:\/\/jv16powertools.com\/blog\/pc-system-utilities-software-testing-weekly-1\/","title":{"rendered":"PC System Utilities Software – Software Testing Weekly #1"},"content":{"rendered":"

Introduction<\/h2>\n

We design and test PC System Utilities for more than 18 years. However, we never showed our customers much of our thought process, except for rare occasions on our pc system utilities forum<\/a>.<\/p>\n

With a new build of jv16 PowerTools in our test lab, while getting ready to release the next product update, we decided to start sharing some of the details about “how the sausage gets made”.<\/p>\n

By reading this post, you will learn more about how jv16 PowerTools\u00a0is being tested for some specific test cases.<\/p>\n

Simple, but sinister!<\/p>\n

Test cases<\/h2>\n

In order to ensure compatibility of our release candidate software version with the most popular 3rd party software products, we usually conduct tests that answer questions similar to the ones described below:<\/p>\n

Test Case #01:\u00a0<\/strong>Do most popular software still start correctly after using jv16 PowerTools > Clean and SpeedUp My Computer?<\/p>\n

This test case is designed to identify any false positives<\/a> that may result from our recent development work on the latest version of the Clean and SpeedUp My Computer tool, part of jv16 PowerTools.<\/p>\n

Test Case #02:<\/strong> What is the improvement in system startup time after using jv16 PowerTools > Startup Optimizer?<\/p>\n

This test case is designed to measure the effectiveness of the Startup Optimizer tool on an operating system with \u00a0lots of bloatware<\/a> installed, some of which automatically start with the operating system.<\/p>\n

Test Environment<\/h2>\n

The current test cases were performed using an Oracle VirtualBox – Version 5.1.22 r115126 (Qt5.7.1) virtual environment running Windows 10 with 4 CPU cores and 8 GB of RAM assigned.<\/p>\n

The virtual machine was run on a host computer running Ubuntu Linux 17.04 LTS (64 bit) with an Intel-i5 processor, 20 GB RAM and a SSD system disk.<\/p>\n

Verifiability<\/h2>\n

All of the past and current test results are accompanied by screenshots and\/or video recordings which have been saved during various testing phases in order to address some of the most common test result credibility concerns for this type of studies.<\/p>\n

Test Case #01: Passed!<\/h2>\n

During the first test case, the following steps were taken:<\/p>\n

Step 1)<\/strong> On a freshly installed Windows 10, some of the most popular 3rd party software were installed. To ease this process, a free mass software installer automation<\/a> by Ninite was used.<\/p>\n

Step 2)<\/strong>\u00a0To make sure that there is some cleaning work to do for our PC System Utilities software, we wanted each of the 3rd party installed software to get a chance at setting their own settings and initial configuration data in the system’s registry.<\/p>\n

Also, we wanted to make sure that each of them actually starts correctly and without errors, before touching the system with jv16 PowerTools.<\/p>\n

Step 3)<\/strong>\u00a0In order to ensure that all 3rd party software have been properly installed, a system reboot was carried out. After which, crap.reg was imported into the system’s registry.<\/p>\n

This Windows registry key\u00a0samples database contains intentionally orphaned leftover traces of random 3rd party software. Meaning, registry keys that are disconnected from their local files.<\/p>\n

This test file was obtained during previous benchmark test reports<\/a> and is currently used in our software testing lab as a high quality\u00a0source of unwanted registry keys.<\/p>\n

We use such data to test the effectiveness of our registry cleaner tool<\/a> as well as our competitors.<\/p>\n

Step 4)<\/strong>\u00a0After the unwanted registry key samples were imported, each software previously installed on Windows was once again run in order to ensure that it still starts correctly.<\/p>\n

Conclusion: 100% of the installed 3rd party software\u00a0still started correctly after the software leftover traces were imported.<\/p>\n

Step 5) <\/strong>jv16 PowerTools 2017 version 4.1.0.1724 (release candidate) was installed and the initial setup performed (mapping and diagnosing the system’s registry and file system in order to determine initial system health scores).<\/p>\n

Step 6)<\/strong>\u00a0Before running Clean and SpeedUp My Computer using its default settings, we took note of the Registry Information tool,\u00a0Home > System Startup Times and Startup Timer > Startups list.<\/p>\n

This should help us to evaluate the effectiveness of jv16 PowerTools for this use case scenario as we will be comparing the same information after cleaning and optimizing the system.<\/p>\n

Step 7)<\/strong>\u00a0jv16 PowerTools 2017 > Clean and SpeedUp My Computer was used in order to identify as many system errors as possible.<\/p>\n

Using its default scanner settings, the registry cleaner component was able to identify the following software leftovers. Some of them have been imported via the crap.reg file described earlier and some of them are the result of improper software package management by Windows.<\/p>\n

Step 8)\u00a0<\/strong>After the Clean and SpeedUp My Computer tool was used, the system was rebooted once in order to ensure that all settings\u00a0take effect.<\/p>\n

After the system was restarted, each software previously installed from Ninite was once again opened in order to ensure that it is still starting correctly (no false positive symptoms after using jv16 PowerTools).<\/p>\n

Test Case #1 conclusion:<\/strong> Test passed! 100% of the installed 3rd party software\u00a0still started correctly after the imported software leftover (for testing purposes)\u00a0were cleaned by the Clean and SpeedUp My Computer tool.<\/p>\n

Test Case #02: Passed!<\/h2>\n

During the second test case, the following steps were taken:<\/p>\n

Step 9)<\/strong>\u00a0After cleaning and optimizing the system using the Clean and SpeedUp My Computer tool, we recorded the information provided by the Registry Information tool as well as the Startup Timer which shows the effectiveness of the Startup Optimizer.<\/p>\n

Before doing so, we rebooted the system at least five times in order to make sure that the Startup Timer tool has sufficient data to calculate the percent in startup time improvement based on data from before and after using the Clean and SpeedUp My Computer tool.<\/p>\n

Step 10)<\/strong>\u00a0Took a screenshot of the Startup Timer – Startups logging panel, a screenshot of Home > System Startup Times as well as a screenshot of the Registry Information > Details (full registry) panel. You can see all of them below.<\/p>\n

Test Case #2 conclusion:<\/strong> Test passed! An average startup time improvement of more than 5% was achieved after using the Startup Optimizer tool.<\/p>\n

Test Cases Summary:<\/h2>\n

Test Case #1 (summary)<\/strong>\u00a0answers the following question for jv16 PowerTools – release candidate 4.1.0.1723:<\/p>\n

Question:<\/strong> Are any of the most popular software affected by the normal operation of the Clean and SpeedUp My Computer tool?<\/p>\n

Answer:<\/strong> None of the most popular software installed using Ninite’s automatic software installed seemed to manifest any false positives with jv16 PowerTools 2017 – version 4.1.0.1723.Test Case #2 (summary)<\/strong>\u00a0answers the following question\u00a0for jv16 PowerTools – release candidate 4.1.0.1723:<\/p>\n

Question: <\/strong>What is the improvement in system startup time after using jv16 PowerTools > Startup Optimizer?<\/p>\n

Answer:<\/strong>\u00a0On average, the test system configuration started<\/strong> 6.94% faster<\/strong>. The result was measured 5 reboots after using the Clean and SpeedUp My Computer tool.<\/p>\n

Related\u00a0weekly benchmark test reports:<\/h2>\n