Custom Task actions You can attach custom build logic that executes before or

Custom task actions you can attach custom build logic

This preview shows page 99 - 107 out of 168 pages.

Custom Task actions You can attach custom build logic that executes before or after a task Custom conventions e.g. Java builds use standard project structures and naming convention You can write your own plugins that provide conventions Custom Model Gradle allows you to introduce new concepts into a build beyond tasks, files and dependency configurations. Concept of Source Set to build. 4. Gradle is Extensible 15-Feb-20 CSI-ZG514 - Intro to Devops 99
Image of page 99
BITS Pilani, Pilani Campus Though Gradle build scripts can be viewed as a code , build scripts describe what steps are needed to build the software, not how those steps should do the work. That’s a job for custom task types and plugins. Avoid putting Conditional logic or very complex task action implementations. 5. Build scripts operate against an API 15-Feb-20 CSI-ZG514 - Intro to Devops 100
Image of page 100
BITS Pilani, Pilani Campus Gradle Vs Maven 15-Feb-20 CSI-ZG514 - Intro to Devops 101
Image of page 101
BITS Pilani Pilani Campus Testing and Test Automation Concepts 15-Feb-20 CSI-ZG514 - Intro to Devops 102
Image of page 102
BITS Pilani, Pilani Campus Run Quicker Can run repeatedly without much additional cost. Return of Investment - in longer term (initial investment to write automation scripts and some maintenance required) Reduce human error Automated test can also be run across multiple platforms, operating systems, and devices Bugs and regressions can be found quickly Giving confidence to developers that updates to the code base didn't break anything. Automated test will create better quality product SW can be released quickly and smoothly with less effort Value Of Automation 15-Feb-20 CSI-ZG514 - Intro to Devops 103
Image of page 103
BITS Pilani, Pilani Campus Different types of tests Unit, integration, component, functional, UI and Performance the list goes on Which type of test to automate? Agile testing quadrants is one such model which you can use to determine which type of test to automate Which tests to Automate? 15-Feb-20 CSI-ZG514 - Intro to Devops 104
Image of page 104
BITS Pilani Pilani Campus Agile Testing Models 15-Feb-20 CSI-ZG514 - Intro to Devops 105
Image of page 105
BITS Pilani, Pilani Campus Developed by Mrian Marick, 2003 . Agile Test Quadrants Model 15-Feb-20 CSI-ZG514 - Intro to Devops 106 @Scaled agile Inc. Q1: Ensure the functionality is working as expected, and that the code has a quality foundation to build upon. Tests in quadrant one are written alongside development, and help to confirm the functionality of the feature as it's being built Q2: These tests help answer questions and discover information about the application. Developed during or after development Q3: are user-oriented and help to understand the user's experience by how they interact with the application. Q3 involves critical thinking and an in-depth observation of the application's workflow Q4: Purpose is to provide targeted information about the application.
Image of page 106
Image of page 107

You've reached the end of your free preview.

Want to read all 168 pages?

  • Winter '19
  • Unit testing, Pilani Campus

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture