[Unattended] Testing new install scripts

[William Faulk]

I'm working on a number of custom installation scripts for my environment,
and am having trouble testing them. I find that testing doesn't work very
well when doing it outside the context of actually installing via
Unattended, and doing a full install takes forever, compared to the
problems with my scripts. That is, an hour of turnaround time to fix a
path problem or syntax error really delays my development.

Does anyone have any tips on doing testing more quickly?

-Bitt Faulk

[Knoll, Bernhard]

Hello,

check out appsonly.bat, it´s been discussed here on the list many times.

Best regards

-----Ursprüngliche Nachricht-----
Von: William Faulk [mailto:***@cortina-systems.com]
Gesendet: Donnerstag, 22. Juli 2010 19:04
An: unattended-***@lists.sourceforge.net
Betreff: [Unattended] Testing new install scripts

I'm working on a number of custom installation scripts for my environment,
and am having trouble testing them. I find that testing doesn't work very
well when doing it outside the context of actually installing via
Unattended, and doing a full install takes forever, compared to the
problems with my scripts. That is, an hour of turnaround time to fix a
path problem or syntax error really delays my development.

Does anyone have any tips on doing testing more quickly?

-Bitt Faulk

[Ben Greenfield]

Post by Knoll, Bernhard
Hello,
check out appsonly.bat, it´s been discussed here on the list many times.

double thumbs up on apps.only it lets you work on one script and try it over and over and over again.

Post by Knoll, Bernhard
Best regards
-----Ursprüngliche Nachricht-----
Gesendet: Donnerstag, 22. Juli 2010 19:04
Betreff: [Unattended] Testing new install scripts
I'm working on a number of custom installation scripts for my environment,
and am having trouble testing them. I find that testing doesn't work very
well when doing it outside the context of actually installing via
Unattended, and doing a full install takes forever, compared to the
problems with my scripts. That is, an hour of turnaround time to fix a
path problem or syntax error really delays my development.
Does anyone have any tips on doing testing more quickly?
-Bitt Faulk
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
unattended-info mailing list
https://lists.sourceforge.net/lists/listinfo/unattended-info
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
unattended-info mailing list
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Sander Nieuwenhuizen]

Use a virtual image with a snapshot based on some virtualization tool. If
the syntax fails, you restart the virtual image from the point you saved
last time.

Succes!

Sander

Post by William Faulk
I'm working on a number of custom installation scripts for my environment,
and am having trouble testing them. I find that testing doesn't work very
well when doing it outside the context of actually installing via
Unattended, and doing a full install takes forever, compared to the
problems with my scripts. That is, an hour of turnaround time to fix a
path problem or syntax error really delays my development.
Does anyone have any tips on doing testing more quickly?
-Bitt Faulk
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
unattended-info mailing list
https://lists.sourceforge.net/lists/listinfo/unattended-info