Forum Discussion
jsc wrote:If there are dependencies (i.e. supplier / product / purchase / receive / customer / sale / receivable...)
how can individual testitems be descrete and reusable and run on their own?
- I do not get what dependencies this could be, but I try to guess.
- e.g. we have a database that we restore where a webservice-connector or other connectors are already defined- we have surrounding testenvironment that provides data (some vm sontaining ppm-systems, excel files, webservices,...) that is either under version control or must not be changed at all.
- is it this what you meant?l.
Examples of dependencies our system:
- Product(s) cannot be created with Supplier(s)
- Purchase Order(s) cannot be created without Product(s)
- Receipts cannot be created without Purchase Order(s)
- Sale(s) cannot be created without Inventory (and Customers)
- Receivable(s) cannot be created without Sale(s)
I understand your approach but have a question. How are you restoring your database while the application pool (IIS) is running? I regularly restore the database to certain pre-defined states (i.e. pre-sales) when there is a failure but this requires stopping the web server application pool and killing an application process before a restore can be performed.
Are you a Microsoft shop? We use IIS and SQL Server (donning fire suit).
william_roe wrote:
- Product(s) cannot be created with Supplier(s)
- Purchase Order(s) cannot be created without Product(s)
- Receipts cannot be created without Purchase Order(s)
- Sale(s) cannot be created without Inventory (and Customers)
- Receivable(s) cannot be created without Sale(s)
I understand your approach but have a question. How are you restoring your database while the application pool (IIS) is running? I regularly restore the database to certain pre-defined states (i.e. pre-sales) when there is a failure but this requires stopping the web server application pool and killing an application process before a restore can be performed.
Are you a Microsoft shop? We use IIS and SQL Server (donning fire suit).
I think we do not have such dependencies, but I would (or at least try to) integrate them in a stable state in our testenvironment.
We use a postgreSQL databases and apacache Tomcat in our web application.
The restoring databases is easy. The service is stopped and started via script as well as the Tomcat service. So we make sure that all services are started properly when login starts.
(in other departments we do similar stuff with MS SQL Server (no problem at all) and Oracle DMBS (bigger and therefore slower to restore)).
No, we are no webshop, we create some sort of ppm-software. (I am not sure if it is allowed to post links to our software here, so I do not...)
- jsc9 years agoRegular Contributor
we do it like this (Jscript)
function startTask(taskname, waitTime)
{
Log.AppendFolder("startTask: " + taskname);
Log.Message("starting task '" + taskname + "'");
var oShell = new ActiveXObject("WSCript.shell");
oShell.run('NET START "' + taskname + '"', "1", true);
Log.Message("trying to start task '" + taskname + "'");
Delay(waitTime);
Log.Message("waited for " + waitTime + " ms");Log.PopLogFolder();
}Stopping a task is the same. But we combine it with checking afterwards if the corresponding process does still exist. If the process still exists it is just killed. (script as well)
- william_roe9 years agoSuper Contributor
jsc wrote:
william_roe wrote:- Product(s) cannot be created with Supplier(s)
- Purchase Order(s) cannot be created without Product(s)
- Receipts cannot be created without Purchase Order(s)
- Sale(s) cannot be created without Inventory (and Customers)
- Receivable(s) cannot be created without Sale(s)
I understand your approach but have a question. How are you restoring your database while the application pool (IIS) is running? I regularly restore the database to certain pre-defined states (i.e. pre-sales) when there is a failure but this requires stopping the web server application pool and killing an application process before a restore can be performed.
Are you a Microsoft shop? We use IIS and SQL Server (donning fire suit).
.... So we make sure that all services are started properly when login starts.
(in other departments we do similar stuff with MS SQL Server (no problem at all) and Oracle DMBS (bigger and therefore slower to restore)).
Sounds as though our next step is to figure out how to start / stop IIS (via script) and how to terminate / launch applications via script.
GREAT DISCUSSIONS!!!
Related Content
Recent Discussions
- 9 hours agovladd1