You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm considering integrating Robocop in my workflow, the project is a test suite focused on evaluating implementations of a network protocol for managing digital certificates. The domain is full of keywords related to security and PKI (public key infrastructure), like: X509, CSR, ASN1, PKIMessage, DER, PBMAC1, PEM, RSA, etc.
Robocop complains about them, because keywords like Get ASN1 value as DER or PKIMessage body type must be don't follow the each_word_capitalized or first_word_capitalized rule.
However, I believe it is better to leave them like this, because these terms are standardized in the corresponding RFCs and are familiar to the domain experts - they are the target audience for reading the reports and writing new test cases.
After reading the documentation, my understanding is that I can add exceptions by defining a regular expression pattern. Considering that there are many terms, it will be a rather complex regexp, which hinders maintainability in the long run. It would be easier if one could define a list of words which can be used "as is" in keywords.
I was wondering about the best way to accommodate this request in the current version of Robocop. Is there a simpler way to accomplish this, which I am not aware of?
The text was updated successfully, but these errors were encountered:
I'm considering integrating Robocop in my workflow, the project is a test suite focused on evaluating implementations of a network protocol for managing digital certificates. The domain is full of keywords related to security and PKI (public key infrastructure), like: X509, CSR, ASN1, PKIMessage, DER, PBMAC1, PEM, RSA, etc.
Robocop complains about them, because keywords like
Get ASN1 value as DER
orPKIMessage body type must be
don't follow theeach_word_capitalized
orfirst_word_capitalized
rule.However, I believe it is better to leave them like this, because these terms are standardized in the corresponding RFCs and are familiar to the domain experts - they are the target audience for reading the reports and writing new test cases.
After reading the documentation, my understanding is that I can add exceptions by defining a regular expression pattern. Considering that there are many terms, it will be a rather complex regexp, which hinders maintainability in the long run. It would be easier if one could define a list of words which can be used "as is" in keywords.
I was wondering about the best way to accommodate this request in the current version of Robocop. Is there a simpler way to accomplish this, which I am not aware of?
The text was updated successfully, but these errors were encountered: