[Bug]: Object Mocking failed when there is a private field type different

[daneshk]

Description

When we have private fields in the Mock object which is not correctly mapped with the field types of the original object, mocking fails giving the following error,

error: incompatible field type 'int' provided for field name
        at ballerina.test.0:mock(mock.bal:309)
           danesh.object_mocking$test.0.tests.init-tests:getMockClient(tests/init-tests.bal:5)

Do we need to validate private fields when we do object mocking?

Steps to Reproduce

You can reproduce the issue with the following source code

Source code

import ballerina/io;

Foo f = initialize();

public function initialize() returns Foo {
    return new Foo();
}

public class Foo {

    private string name;
    public function foo() {
        io:println("Hello, Foo!");
    }
    
}

public class Bar {

    private int name;
    public function foo() {
        io:println("Hello, Bar!");
    }

}

public function main() {
    io:println("Hello, World!");
}

Test code

import ballerina/test;

@test:Mock {functionName: "initialize"}
isolated function getMockClient() returns Foo {
    return test:mock(Foo, new Bar());
}

Affected Version(s)

Latest Ballerina versions

OS, DB, other environment details and versions

No response

Related area

--> Testerina

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[daneshk]

Can we get this fixed with update 10 please, as it is blocking the feature ballerina-platform/ballerina-library#5840

[Dilhasha]

Can we get this fixed with update 10 please, as it is blocking the feature ballerina-platform/ballerina-library#5840

Ack.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.