YAxUnit

YAxUnit provides several auxiliary modules designed to simplify test development by extending the core engine's capabilities. These modules cover data retrieval, collection manipulation, string processing, logging, object creation, and error handling.

Available auxiliary modules include:

• ЮТЗапрос (queries.md): Methods for retrieving data from the information database.
• ЮТКоллекции (collections.md): Universal methods for working with various collections such as arrays, tables, and structures.
• ЮТСтроки (/api/ЮТСтроки): Universal methods for string manipulation.
• ЮТЛогирование (/api/ЮТЛогирование): Logging methods.
• ЮТФабрика (/api/ЮТФабрика): Methods for creating various engine objects required during test development.
• ЮТКомпоненты (/api/ЮТКомпоненты): Provides access to external engine components.
• ЮТМетаданные (/api/ЮТМетаданные): Methods for working with metadata.
• ЮТРегистрацияОшибок (/api/ЮТРегистрацияОшибок): Methods for error registration and handling.
• ЮТИсключения (/api/ЮТИсключения): Methods for formatting exception messages.

YAxUnit is a powerful testing tool designed for solutions built on the 1C:Enterprise platform. It is built following testing best practices and provides a comprehensive suite of features to streamline the development and verification of 1C code.

Key capabilities include:

• Test Engine: Executes tests and generates detailed reports in various formats.
• Assertions: Provides tools to verify expected results against actual outcomes, ensuring precision in testing.
• Test Data Management: Powerful tools for creating, deleting, and searching for required test data.
• Fluent API: Supports fluent expressions to make test code more readable, understandable, and maintainable.
• Extensibility: Allows developers to extend functionality to meet unique project requirements.
• EDT Plugin: A dedicated plugin for 1C:Enterprise Development Tools (EDT) that enables running and debugging tests with a single click.

Mockito is a module inspired by the Java Mockito framework. It allows you to change system behavior by replacing method results, disabling algorithms, or bypassing checks. This is useful for testing code that depends on external systems, verifying method parameters, or isolating specific logic.

Capabilities:

• Change method behavior: Specify return values, throw exceptions, or prevent execution.
• Configure conditions: Set conditions for method parameters so changes apply only in specific cases.
• Mock private and exported methods: Mock public and private methods of objects, documents, catalogs, etc.
• Collect statistics: Observe method calls to ensure they are executed with correct parameters.

Limitations:

• Cannot execute arbitrary logic during a method call.
• Cannot change method parameters.
• Cannot store call results during statistics collection.
• Scope: Mockito works via configuration method borrowing (&Вместо). It can only mock methods defined within the configuration itself. It cannot mock:
  • Platform methods (built-in 1C methods).
  • Extension methods.
  • Methods of external processing or reports.

ТелоОтвета = Новый Структура("success": Истина);
// Настройка мокирования
Мокито.Обучение(РаботаСHTTP)
  .Когда("ОтправитьЗапрос").Вернуть(
    ЮТест.Данные().HTTPОтвет()
      .УстановитьКодСостояния(200)
      .УстановитьТело(ТелоОтвета))
  .Прогон();

// Тестовый прогон
Результат = РаботаСHTTP.ОтправитьЗапрос("https://example.com");

// Проверка
ЮТест.ОжидаетЧто(Результат.КодСостояния).Равно(200);

In YAxUnit, assertions are used to describe and verify expectations (requirements) for the functionality being tested. Instead of manually checking conditions with If statements and throwing exceptions, you use the ЮТест.ОжидаетЧто() mechanism.

Using assertions provides several benefits:

1. Readable Tests: Method chains form human-readable sentences.
2. Clear Error Messages: When an assertion fails, YAxUnit generates detailed, "friendly" error messages that explain exactly what was expected versus what was actually received.
3. Error Differentiation: Assertion failures are marked as a specific type of error, allowing you to distinguish between a failed expectation (the test logic is correct, but the system behavior changed) and a code crash (an actual exception in the system under test).

To improve maintainability, use indentation and formatting for long assertion chains, and avoid writing excessive assertions that aren't necessary for the specific test scenario.

ЮТест.ОжидаетЧто(ДанныеЗаписи)
    .Свойство("Поставщик").Равно(ДанныеОбъекта.Поставщик)
    .Свойство("Товары")
        .ИмеетДлину(1)
        .Свойство("Товары[0].НомерСтроки").Равно(2)
        .Свойство("Товары[0].Товар").Равно(ДанныеОбъекта.Товары[0].Товар);