Archive for the ‘SOFTWARE TESTING’ Category

Can Programming Be Strictly Portable Relative To Language?

September 18, 2015

The activity associated with development of strictly portable methods of software development will be presented here. Included in this Portability effort will be Windows based C, C++, C#, and Visual Basic; and Linux based C and C++.

THURSDAY: 2013/09/17

STATUS: The write and verification test files have been prepare and are ready to be used to both check out and thoroughly test the common program output library.

DETAIL: This library has both the capability of writing an output file and verifying that a previously created file has not been modified.

RESULTS: The need to thoroughly test the library has resulted in test files that were much larger and more complicated than expected. The conditional test library needs to be upgraded.

NEXT TASK: The next task will be to prepare the test task definition files and start performing the tests.

Certifiable Test Methods

July 30, 2015

The activity associated with the development of certifiable test
processes will be presented in this blog.

The conditional test library has provided a good means of checking out
a library product. Currently, it does not produce a certifiable report.

A FAT (First Article Test) and FACT (Factory Acceptance Test) require
that a test report be prepared. Furthermore, this test report must
certifiable relative to the library product and that it has not be
altered.

THURSDAY: 2015/07/30

STATUS: The Conditional Test Library currently prepares a source file
for each set test condition for performing the specific test.

DETAIL: This source file is generated from the 128-Monte Carlo Test
bits in the “Define Test Step” of the Test Project. It has used in the
“Test Program Step”.

NEXT TASK: The subject library must be modified to render it capable of
preparing the report generation source in for the “Record Result Step”.
This report file must equipped with pseudo random parity bits to permit
certification.

Developing a Website using a software parts library

April 7, 2015

The activity associated with development of a software parts library for the development of a web-site will be presented here. This will be an extension of the library used to prepare Programmable Software Development Environment manual.

This effort was started a long time ago following the development of the manual software parts library. Its purpose was to eliminate the need for Front Page. It was subsequently put on hold so that other more important efforts could proceed.

Mr. Mike is a long time professional friend of mine who has recently offered to reconstruct my Web-Site. I told him my plan to use my tool to rebuild my site. He has had difficulties relating to my technology (It is quite different than normal programming methods) and I am not really skilled in Web-site design. We both felt that this might a great opportunity to make the technical connection.

TUESDAY: 2015/04/07

STATUS: Now that the Programmable Software Development Environment error has been corrected, this project will be restarted

DETAIL: A Programmable Software Development Environment system error was encountered while attempting to redefine the CSS software parts library from a set of small software parts libraries. This redefinition process will greatly improve the capability of thoroughly testing the resulting product.

RESULTS: The software parts files containing only the _INCLUDE commands, needed for this redefinition process, are now usable in all software parts library versions (experimental, alpha, beta, and release).

MY NEXT TASK: My next task is to develop a names management and communication library and integrate it into both the CSS and HTML software parts libraries.

Economical Rigorous Software Testing at All Levels

August 10, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

FRIDAY: A local script only exists in the task in which it was created. It is discarded when this task is complete. A global script that calls a local script in a particular task will fail to execute in a subsequent task.  The associated error is now properly reported. The single line this script calling capability for global and local scripts has now been sufficiently tested that it can been used for manual development.

SATURDAY: To determine what additional changes are needed to the script software parts library, I need to answer the question: How much is the script going to simulate a macro?  In the past, I made a limited effort. Maybe a complete simulation is needed. I will re-examine this question

MONDAY: To make the script simulate a macro, I will need to improve the script calling arguments and return capabilities, and both the automatic and global data storage. I have tentatively decided to proceed with the update.  The script calling arguments will be first. The planned improvement will include a parameter capability for the _RUN_SCRIPT macro.

Economical Rigorous Software Testing at All Levels

August 3, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

FRIDAY: The single line macro-loading local-script (script defined in the same task as it is executed) software parts of the script software parts library have been modified and formally tested. These commands load the macro name and up to four arguments into a specified local script so that they will be executed when the script is executed. The formal testing of the single line macro-loading global (capable of being executed in a later task than defined) is next.

SATURDAY: The single line macro-loading global-script (capable of being executed in a later task than defined) software parts of the script software parts library have been modified and formally tested. The formal testing of multi-line equivalent macro-loading software parts is next.  These parts enable macros with more than four arguments to be loaded into a script.

MONDAY: The formal testing of both the global and local multi-line equivalent macro-loading software parts has been successfully completed. I believe that the corrections required for the testing of the common-include software parts library has been accomplished.  My next step is to verify my assessment and to update the status of the script software parts library relative to the manual upgrade.

TUESDAY: A script is capable of calling another script. The software parts library associated with manual development uses this script calling capability. The formal testing of this capability has been started. An error reporting deficiency has already been detected and will be corrected.

WEDNESDAY: A local script only exists in the task in which it was created. It is discarded when this task is complete. A global script that calls a local script in a particular task will fail to execute in a subsequent task.  The associated error is not properly reported. The necessary corrections will be made next.

Economical Rigorous Software Testing at All Levels

May 18, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

SATURDAY: The formal tests of the cryptographic software parts library has been completed.  This library will be used in several applications.

Economical Rigorous Software Testing at All Levels

May 11, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.

MONDAY: One of my minor project is the development of a cryptographic software parts library for securing of various text files. A requirement of this cryptographic software parts library is to reliably error-out if the wrong key was used during decryption. The desire to thoroughly test this library caused me to seriously update the concept.

TUESDAY: The revised version of the cryptographic software parts library has been prepared and is ready for a comprehensive test.

THURSDAY: The revised version of the cryptographic software parts library has been functionally tested.  The testing process will continue.

Economical Rigorous Software Testing at All Levels

May 4, 2012

The ability to thoroughly and economically test software work-products at all levels is a necessary requirement of the error-free software development process.  The Programmable Software Development Environment has a Monte-Carlo (random generator) based test system which is capable of satisfying this requirement.

Historically, this tool has been very difficult to set up and hence has only been experimentally use. Recently, a library of software parts has been developed which greatly simplifies its use. As a consequence, it is being successfully used in the checkout and formal testing required in my portable software development research and development activity.

This blog will be used to focus upon on my test related research and development efforts.