Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate test_analysisd documentation to QA Docs #1834

Merged
merged 2 commits into from
Sep 3, 2021
Merged

Migrate test_analysisd documentation to QA Docs #1834

merged 2 commits into from
Sep 3, 2021

Conversation

mdengra
Copy link
Contributor

@mdengra mdengra commented Sep 2, 2021

Related issue
Closes #1804

Description

As part of epic #1796, this PR adds the missing documentation and migrates the current documentation to the new format used by QA Docs.
The used schema is provisional (third proposal of issue #1694) until we have the definitive one.

Docs example

test_check_rare_socket_responses.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `wazuh-db` and `analysisd` daemons correctly
  handle `syscheck` events considered rare.
group_id: 10
id: 11
name: test_check_rare_socket_responses.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the output logs are consistent with the syscheck events received.
  description: Validate every response from the `analysisd` socket to the `wazuh-db`
    socket using rare `syscheck` events with encoded characters.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_rare_events.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_rare_events.yaml` file."
  name: test_validate_rare_socket_responses
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_rare_events.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 2
type: integration

test_check_socket_responses.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `wazuh-db` and `analysisd` daemons correctly
  handle common `syscheck` events.
group_id: 10
id: 13
name: test_check_socket_responses.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the output logs are consistent with the syscheck events received.
  description: Validate every response from the `analysisd` socket to the `wazuh-db`
    socket using common `syscheck` events.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_events.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_events.yaml` file."
  name: test_validate_socket_responses
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_events.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 2
type: integration

test_validate_linux_analysisd_alerts.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `analysisd` daemon correctly handles alerts
  generated from the received Linux events.
group_id: 10
id: 14
name: test_validate_linux_analysisd_alerts.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the alerts generated are consistent with the events received.
  description: Check that the alerts generated by `analysisd` from Linux systems events
    are valid. The `validate_analysis_alert_complex` function checks if an `analysisd`
    alert is properly formatted in reference to its `syscheck` event.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_events.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_events.yaml` file."
  name: test_validate_all_linux_alerts
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - generate_events_and_alerts:
      brief: Read the specified yaml and generate every event and alert using the
        input from every test case.
      type: fixture
  - get_alert:
      brief: List of alerts to be validated.
      type: fixture
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_events.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 2
type: integration

test_validate_rare_analysisd_alerts.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `analysisd` daemon correctly handles alerts
  generated from the received Linux events considered rare.
group_id: 10
id: 12
name: test_validate_rare_analysisd_alerts.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the alerts generated are consistent with the events received.
  description: Check that the alerts generated by `analysisd` from Linux systems events
    considered rare are valid. The `validate_analysis_alert_complex` function checks
    if an `analysisd` alert is properly formatted in reference to its `syscheck` event.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_rare_events.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_rare_events.yaml` file."
  name: test_validate_all_linux_alerts
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - generate_events_and_alerts:
      brief: Read the specified yaml and generate every event and alert using the
        input from every test case.
      type: fixture
  - get_alert:
      brief: List of alerts to be validated.
      type: fixture
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_rare_events.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 2
type: integration

test_validate_win32_analysisd_alerts.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `analysisd` daemon correctly handles alerts
  generated from the received Windows events.
group_id: 10
id: 16
name: test_validate_win32_analysisd_alerts.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the alerts generated are consistent with the events received.
  description: Check that the alerts generated by `analysisd` from Windows systems
    events are valid. The `validate_analysis_alert_complex` function checks if an
    `analysisd` alert is properly formatted in reference to its `syscheck` event.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_events_win32.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_events_win32.yaml` file."
  name: test_validate_all_win32_alerts
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - generate_events_and_alerts:
      brief: Read the specified yaml and generate every event and alert using the
        input from every test case.
      type: fixture
  - get_alert:
      brief: List of alerts to be validated.
      type: fixture
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_events_win32.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 2
type: integration

test_validate_win32_analysisd_registry_alerts.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will verify if the `analysisd` daemon correctly handles alerts
  generated from the received Windows registry-related events.
group_id: 10
id: 15
name: test_validate_win32_analysisd_registry_alerts.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_all_syscheckd_configurations/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the alerts generated are consistent with the events received.
  description: Check that the alerts generated by `analysisd` from Windows systems
    registry-related events are valid. The `validate_analysis_alert_complex` function
    checks if an `analysisd` alert is properly formatted in reference to its `syscheck`
    event.
  logging:
  - ossec.log:
    - Multiple values located in the `syscheck_events_win32.yaml` file.
  - alerts.json: -"Multiple values located in the `syscheck_events_win32.yaml` file."
  name: test_validate_all_win32_registry_alerts
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - generate_events_and_alerts:
      brief: Read the specified yaml and generate every event and alert using the
        input from every test case.
      type: fixture
  - get_alert:
      brief: List of alerts to be validated.
      type: fixture
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (syscheck_events_win32.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 4.1
tiers:
- 2
type: integration

test_error_messages.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will check if the `analysisd` daemon handles correctly the
  invalid events it receives.
group_id: 10
id: 19
name: test_error_messages.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_error_messages/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the error messages generated are consistent with the events received.
  description: Check if when the `analysisd` socket receives a message with an invalid
    event, it generates the corresponding error that sends to the `wazuh-db` socket.
  logging:
  - ossec.log:
    - Multiple values located in the `error_messages.yaml` file.
  name: test_error_messages
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (error_messages.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 0
type: integration

test_event_messages.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will check if the `analysisd` daemon correctly handles incoming
  events related to file modification.
group_id: 10
id: 17
name: test_event_messages.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_event_messages/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the alerts generated are consistent with the events received.
  description: Check if when the `analysisd` socket receives a message with a file
    modification-related event, it generates the corresponding alert that sends to
    the `wazuh-db` socket. The `validate_analysis_alert` function checks if an `analysisd`
    event is properly formatted.
  logging:
  - ossec.log:
    - Multiple values located in the `event_messages.yaml` file.
  - alerts.json: -"Multiple values located in the `event_messages.yaml` file."
  name: test_event_messages
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (event_messages.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 0
type: integration

test_integrity_messages.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will check if the `analysisd` daemon correctly handles incoming
  events related to file integrity.
group_id: 10
id: 20
name: test_integrity_messages.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_integrity_messages/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the messages generated are consistent with the events received.
  description: Check if when the `analysisd` socket receives a message with a file
    integrity-related event, it generates the corresponding alert that sends to the
    `wazuh-db` socket. The `validate_analysis_integrity_state` function checks if
    an `analysisd` integrity message is properly formatted.
  logging:
  - ossec.log:
    - Multiple values located in the `integrity_messages.yaml` file.
  - alerts.json:
    - Multiple values located in the `integrity_messages.yaml` file.
  name: test_integrity_messages
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (integrity_messages.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 0
type: integration

test_mitre_check_alert.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: Check if `analysisd` generates alerts enriching its fields with `MITRE`
  information. The objective consists on checking if `analysisd` can generate alerts
  using custom rules that contains the `mitre` field to enrich those alerts with MITREs
  IDs, techniques and tactics.
group_id: 10
id: 18
name: test_mitre_check_alert.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_mitre/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the `MITRE` alerts are generated and that they are correct.
  description: Check if `MITRE` alerts are syntactically and semantically correct.
  logging:
  - ossec.log:
    - r".*Ossec server started.*"
  - alerts.json: -"Multiple alerts related to MITRE events."
  name: test_mitre_check_alert
  parameters:
  - get_configuration:
      brief: Get configurations from the module.
      type: fixture
  - configure_local_rules:
      brief: Configure a custom rule in `local_rules.xml` for testing.
      type: fixture
  - restart_wazuh_alerts:
      brief: Reset `alerts.json` and start a new monitor.
      type: fixture
  tags: null
  test_input: Different test cases that are contained in external `XML` files (data
    directory) that include both valid and invalid rules for detecting `MITRE` events.
  wazuh_min_version: 4.0
tiers:
- 0
type: integration

test_scan_messages.yaml 

component: manager
copyright: 'Copyright (C) 2015-2021, Wazuh Inc.

  Created by Wazuh, Inc. <info@wazuh.com>.

  This program is free software; you can redistribute it and/or modify it under the
  terms of GPLv2'
coverage: null
daemons:
- analysisd
- syscheckd
- wazuh-db
description: These tests will check if the `analysisd` daemon correctly handles incoming
  events related to file scanning.
group_id: 10
id: 21
name: test_scan_messages.py
os_support:
- linux, rhel5
- linux, rhel6
- linux, rhel7
- linux, rhel8
- linux, amazon linux 1
- linux, amazon linux 2
- linux, debian buster
- linux, debian stretch
- linux, debian wheezy
- linux, ubuntu bionic
- linux, ubuntu xenial
- linux, ubuntu trusty
- linux, arch linux
path: tests/integration/test_analysisd/test_scan_messages/
pytest_args: null
tags: null
tests:
- assertions:
  - Check that the messages generated are consistent with the events received.
  description: Check if when the `analysisd` socket receives a message with a file
    scanning-related event, it generates the corresponding alert that sends to the
    `wazuh-db` socket.
  logging:
  - ossec.log:
    - Multiple values located in the `scan_messages.yaml` file.
  - alerts.json: -"Multiple values located in the `scan_messages.yaml` file."
  name: test_scan_messages
  parameters:
  - configure_sockets_environment:
      brief: Configure environment for sockets and MITM.
      type: fixture
  - connect_to_sockets_module:
      brief: Module scope version of `connect_to_sockets` fixture.
      type: fixture
  - wait_for_analysisd_startup:
      brief: Wait until analysisd has begun and alerts.json is created.
      type: fixture
  - test_case:
      brief: List of tests to be performed.
      type: list
  tags: null
  test_input: Different test cases that are contained in an external `YAML` file (scan_messages.yaml)
    that includes `syscheck` events data and the expected output.
  wazuh_min_version: 3.12
tiers:
- 0
type: integration

Tests

  • Python codebase satisfies PEP-8 style style guide. pycodestyle --max-line-length=120 --show-source --show-pep8 file.py.
  • The DocGenerator sanity check test does not return errors. python3 DocGenerator.py -s

@mdengra
doc: Create test_analysisd/test_all_syscheckd_configurations missing …
578d111 
…documentation in QA Docs style

The following tests have been documented:
  * test_check_rare_socket_responses.py
  * test_check_socket_responses.py
  * test_validate_linux_analysisd_alerts.py
  * test_validate_rare_analysisd_alerts.py
  * test_validate_win32_analysisd_alerts.py
  * test_validate_win32_analysisd_registry_alerts.py
The scheme of proposal 3 has been used until the definitive one is available.
Update DocGenerator/config.yaml
PEP-8 fixes

Closes: #1804
@mdengra
doc: Create/migrate test_analysisd documentation in QA Docs style
0a9d0e2 
The following tests have been documented:
  * test_error_messages/test_error_messages.py
  * test_event_messages/test_event_messages.py
  * test_integrity_messages/test_integrity_messages.py
  * test_analysisd/test_scan_messages/test_scan_messages.py
Migrated test_mitre/test_mitre_check_alert.py
The scheme of proposal 3 has been used until the definitive one is available.
PEP-8 fixes

Closes: #1804
@mdengra mdengra self-assigned this Sep 2, 2021
@mdengra mdengra linked an issue Sep 2, 2021 that may be closed by this pull request
qa-docs: Migrate test_analysisd documentation to schema 1.0 #1804
Closed
20 tasks
@mdengra mdengra merged commit 680b00e into 1796-migrate-doc-schema-1 Sep 3, 2021
@mdengra mdengra deleted the 1804-qadocs-migrate-test-analysisd branch September 3, 2021 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@roronoasins roronoasins roronoasins approved these changes

Assignees

@mdengra mdengra

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

qa-docs: Migrate test_analysisd documentation to schema 1.0
2 participants
@mdengra @roronoasins