)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":12395,"name":"Roman Vasylets","email":"pomeo92@gmail.com","username":"rvasilets"},"change_message_id":"fd677064feadf9987793bec38e2d5adf1c8f85d7","unresolved":false,"context_lines":[{"line_number":9,"context_line":"In unittesttools, assertDictEqual() and assertEqual()"},{"line_number":10,"context_line":"are implemented by using \u0027!\u003d\u0027 operator. But assertEqual()"},{"line_number":11,"context_line":"can handle dict, list, set and so on. So we should use"},{"line_number":12,"context_line":"assertEqual() to make the test simpler"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: Id9f08ab6f4e3c6c2f68b91aa2dffc80a81ba11a2"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1ac06dbe_57cf4e55","line":12,"updated":"2016-08-24 08:08:46.000000000","message":"No. We use more wide assertion in place where possible to use more specific(I guess developers of assertDictEqual work not for nothing). We should use proper assertion for that purpose","commit_id":"1cdfa578ca6dc28ec77735bca42fe4e48ae88c54"}]}