Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion tests/14account/02deactivate.pl
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,15 @@ sub matrix_deactivate_account

my $body = decode_json $resp->content;

assert_json_keys( $body, qw( error errcode params completed flows ));
assert_json_keys( $body, qw( error errcode params flows ));

my $errcode = $body->{errcode};

$errcode eq "M_FORBIDDEN" or
die "Expected errcode to be M_FORBIDDEN but was $errcode";

exists $body->{completed} and die "Got an unexpected 'completed' key";

Comment on lines +53 to +54
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not entirely convinced that the presence of completed should be a failure here.

I agree that completed should not be required.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems the test I did against synapse was something else. It seems synapse returns: "completed":[], which makes sense.

I guess this is an other case where the specification isn't really clear.

Future->done(1);
});
};
Expand Down