ARTOS Tutorial

• Introduction
  • ARTOS (Art of System Testing)
  • Framework glossary
  • Abbreviations
  • Annotations
  • Example test case and unit
• Artos feature highlight
• Contribution Guidelines

System Setup:

• 1. System Setup
  • 1.1. System requirements
  • 1.2. Add Artos Jar as a dependency
  • 1.3. Eclipse IDE
  • 1.4. IntelliJ IDE

Get Started with Sample Project:

• 1. Get Started with Sample Project

Step-by-Step Guide:

• 1. Implement Project
  • 1.1. Recommended Project Structures
• 2. Implement Runner
• 3. Implement TestCase and TestUnits
• 4. Test Sequence
  • 4.1. Sequence benefits
  • 4.2. Ordering process
  • 4.3. Ignoring sequence assignment
  • 4.4. Test sequence override via test script
  • 4.5. Test sequence override via Runner
  • 4.6. Override priority
• 5. Launch test suite with test-script
  • 5.1. Launch project jar (Windows command-line)
  • 5.2. Launch Maven project as unit test framework
  • 5.3. Runner launch using test script (Eclipse IDE)
• 6. Launch test suite without test-script
  • 6.1. Launch project jar (Windows command-line)
  • 6.2. Launch Maven project as unit test framework
  • 6.3. Runner launch using test script (Eclipse IDE)
• 7. Execute Test Cases
• 8. Test Result
  • 8.1. Console log example

Step-by-Step BDD:

• 1. System Setup
  • 1.1. System requirements
  • 1.2. Add Artos Jar as a dependency
  • 1.3. Eclipse IDE
  • 1.4. IntelliJ IDE
• 2. Implement Project
  • 2.1. Recommended Project Structures
• 3. Implement Feature File
  • 3.1. Sample Feature File
  • 3.2. Feature File Components
• 4. Implement Runner

Concept & Feature:

• Test Suite & Test Runner
  • Scan Scope
  • The Runner
  • Test Suite
• Test Status and Outcome
  • TestUnit vs TestCase Status
• Test Context
  • Context example
• Framework Configuration
  • <organization_info>
  • <logger>
  • <smtp_settings>
  • <dashboard>
  • <features>
• Importance Indicator
  • Importance Indicator in console failure highlights
  • Importance Indicator in summary report
• Failure-Highlights
  • Failure-Highlights Example
• Logging Framework
  • Log files
  • Test report
  • Log File Path and Naming Convention
  • Log Format
  • Log Pattern
  • Log Rollover Policy
  • Log Level
  • Runtime Log Enable/Disable
  • Log File Tracking
  • FAIL Stamp Injection
  • Parameterized logging
• Extent Report

How To:

• Generate Default Configurations
• Use Command line Parameters
  • Example 1: Run from compiled classes
  • Example 2: Run from Jar
  • Above examples are created using below project structure:
• TestScript
  • <configuration version=”1”>
  • <suite>
  • <tests>
  • <parameters>
  • <testcasegroups>
  • <testunitgroups>
  • Auto Generate test script
• Parallel Suite Execution
• TCP Server (Single Client)
  • Simple server
  • Simple server with timeout
  • Server with message filter
  • Server with message parser (fused message parser)
  • Server real-time log
• Visual Regression
  • Original Image capture
  • Modified Image capture
  • Diff => Original and Modified Images

Information:

• @BeforeTestUnit @AfterTestUnit
  • @BeforeTestUnit
  • @AfterTestUnit
• @TestCase
  • Annotation use case(s)
  • Example test case
• @Unit
  • Annotation use case(s)
  • Example test unit
• @TestPlan
  • Annotation use cases
  • Example test case
• @ExpectedException
  • Test combinations and expected outcome
  • Annotation use cases
  • Example usage
• @TestDependency
  • Annotation use case(s)
  • Example test case
• @UnitDependency
  • Annotation use case(s)
  • Example test case
• @DataProvider
  • Annotation use case(s)
  • DataProvider Samples
  • Bind DataProvider to unit

Third Party Integration:

• Report Portal Integration with Artos
  • Preparation
  • Create Listener for Artos
  • Register listener to the Artos runner

Publication:

• Articles
• Blogs