Studio:Why use a scripting language?: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Text replace - 'Category:Scripting' to 'Category:Studio:Scripting') |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Due to their interpretive nature, scripting languages are very dynamic and flexible. Test applications can be quickly implemented through scripts, and these tests can be modified, added, or deleted without requiring time-consuming target software builds. Also, for regression and continuous integration, scripts can be easily automated and executed without constantly requiring new test code to be downloaded or unloaded from the target, which in many cases is impractical or impossible. | Due to their interpretive nature, scripting languages are very dynamic and flexible. Test applications can be quickly implemented through scripts, and these tests can be modified, added, or deleted without requiring time-consuming target software builds. Also, for regression and continuous integration, scripts can be easily automated and executed without constantly requiring new test code to be downloaded or unloaded from the target, which in many cases is impractical or impossible. | ||
[[Category:FAQ]] | [[Category:Studio:FAQ]] | ||
[[Category:Studio:Scripting]] | |||
Latest revision as of 23:46, 20 August 2009
Due to their interpretive nature, scripting languages are very dynamic and flexible. Test applications can be quickly implemented through scripts, and these tests can be modified, added, or deleted without requiring time-consuming target software builds. Also, for regression and continuous integration, scripts can be easily automated and executed without constantly requiring new test code to be downloaded or unloaded from the target, which in many cases is impractical or impossible.