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
This request is for improving integration testing. Currently, integration testing analyzes text files ('.gitignore', '.gitattributes', '.ps1', '.psm1', '.psd1', '.json', '.xml', '.cmd', '.mof', '.md', '.js', '.yml') with several tests such as looking for empty files, Unicode encoding, content with tab characters, and files that do not end with a newline character. A better approach is to select which tests are appropriate for each file type. For example, a .xml file doesn't have to end with a newline and it is irrelevant if it contains a tab character, but it shouldn't be an empty file or be Unicode-encoded.
The text was updated successfully, but these errors were encountered:
@athaynes - I have been buried up to my eyeballs on the current team I'm on, so, no, I haven't made additional progress. I probably should take an hour and wrap up what I was working on and commit it. Are you seeing customer inquiries or demand?
This request is for improving integration testing. Currently, integration testing analyzes text files ('.gitignore', '.gitattributes', '.ps1', '.psm1', '.psd1', '.json', '.xml', '.cmd', '.mof', '.md', '.js', '.yml') with several tests such as looking for empty files, Unicode encoding, content with tab characters, and files that do not end with a newline character. A better approach is to select which tests are appropriate for each file type. For example, a .xml file doesn't have to end with a newline and it is irrelevant if it contains a tab character, but it shouldn't be an empty file or be Unicode-encoded.
The text was updated successfully, but these errors were encountered: