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.

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

[RiskIQ - PassiveTotal] Enhance Connector Functionality and Add Tests #2973

Open
helene-nguyen opened this issue Nov 15, 2024 · 0 comments
Open
Assignees
Labels
filigran team use to identify PR from the Filigran team technical improvement Technical refactor or improvement is needed

Comments

@helene-nguyen
Copy link
Member

Description

Enhance Connector Functionality and Add Tests in the RiskIQ connector

Why Enhance the Connector and Implement Tests?

  1. Improve Reliability: Adding tests ensures that the connector behaves as expected and prevents the introduction of new bugs during future updates.

  2. Ensure Robustness: With comprehensive tests in place, we can verify edge cases and complex scenarios, making the connector more resilient to unexpected inputs or changes in upstream APIs.

  3. Facilitate Maintenance: Well-tested code is easier to refactor and maintain. Future contributors will have confidence that their changes do not break existing functionality.

  4. Increase User Confidence: Users will trust the connector more when they know it has been thoroughly tested and is reliable.

  5. Standardize Practices: Improving the connector aligns it with best practices, including code quality, modularity, and automated testing, which are essential for long-term sustainability.

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. OpenCTI client: { e.g. frontend or python }
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

Actual Output

Additional information

Screenshots (optional)

@helene-nguyen helene-nguyen added filigran team use to identify PR from the Filigran team technical improvement Technical refactor or improvement is needed labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team technical improvement Technical refactor or improvement is needed
Projects
None yet
Development

No branches or pull requests

2 participants