Skip to content

Conversation

Ashuaidehao
Copy link
Collaborator

Relate #287.

@Jim8y
Copy link
Contributor

Jim8y commented Nov 21, 2023

@cschuchardt88

Copy link
Member

@cschuchardt88 cschuchardt88 left a comment

Choose a reason for hiding this comment

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

Do we need test/test-collector/testFiles folder? Isn't that generated when dotnet test. If you don't know than we can keep it.

"isRoot": true,
"tools": {
"neo.express": {
"version": "3.5.19",
Copy link
Member

Choose a reason for hiding this comment

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

can you update to new versions? Same for one below.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

OK

Comment on lines 1 to 28

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 17
VisualStudioVersion = 17.0.31903.59
MinimumVisualStudioVersion = 10.0.40219.1
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "contract", "src\contract.csproj", "{524B2C6C-4354-42E7-A911-F55D877D7F0E}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "contract-test", "test\contract-test.csproj", "{1E87FB71-E3AD-444C-884D-E511758F9E9F}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
{524B2C6C-4354-42E7-A911-F55D877D7F0E}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{524B2C6C-4354-42E7-A911-F55D877D7F0E}.Debug|Any CPU.Build.0 = Debug|Any CPU
{524B2C6C-4354-42E7-A911-F55D877D7F0E}.Release|Any CPU.ActiveCfg = Release|Any CPU
{524B2C6C-4354-42E7-A911-F55D877D7F0E}.Release|Any CPU.Build.0 = Release|Any CPU
{1E87FB71-E3AD-444C-884D-E511758F9E9F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{1E87FB71-E3AD-444C-884D-E511758F9E9F}.Debug|Any CPU.Build.0 = Debug|Any CPU
{1E87FB71-E3AD-444C-884D-E511758F9E9F}.Release|Any CPU.ActiveCfg = Release|Any CPU
{1E87FB71-E3AD-444C-884D-E511758F9E9F}.Release|Any CPU.Build.0 = Release|Any CPU
EndGlobalSection
EndGlobal
Copy link
Member

Choose a reason for hiding this comment

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

Remove this and add to neo-express.sln in a new folder under test called samples?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I find this directory are more like an example to show how to use the neo-test tools, even not a part of unit tests.
Maybe we should move it the root directory with a samples folder? It does not make sence to be placed here.

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good, that makes more sense.

<NeoContractName>$(AssemblyName)</NeoContractName>
<NeoExpressBatchFile>../express.batch</NeoExpressBatchFile>
<Nullable>enable</Nullable>
<TargetFramework>net6.0</TargetFramework>
Copy link
Member

Choose a reason for hiding this comment

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

after tools is updated, can you change this to dotnet 7.0 or you can create a Directory.Build.props file in the test folder?

<IsPackable>false</IsPackable>
<Nullable>enable</Nullable>
<RootNamespace>ContractTests</RootNamespace>
<TargetFramework>net6.0</TargetFramework>
Copy link
Member

Choose a reason for hiding this comment

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

Update to dotnet 7.0

@Ashuaidehao
Copy link
Collaborator Author

Do we need test/test-collector/testFiles folder? Isn't that generated when dotnet test. If you don't know than we can keep it.

These files was contained in origin repo and seems to be used in code. I think we can keep it for now.

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<NeoTestVersion>3.5.17</NeoTestVersion>
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't we add reference to this project?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

OK

Copy link
Collaborator Author

@Ashuaidehao Ashuaidehao Nov 22, 2023

Choose a reason for hiding this comment

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

I find this property could be used in test.yml, changing it back to non hardcoded version.

@cschuchardt88
Copy link
Member

what i mean is, reference the project from the repo not from nuget

@Ashuaidehao
Copy link
Collaborator Author

repo

It's a independent solution for using and testing the nuget package, I think it's not fit to reference other peojects directly.

@Jim8y
Copy link
Contributor

Jim8y commented Nov 22, 2023

All tests passes. I would merge it. If any issues need to be fixed. Can be fixed in another pr.

@Jim8y Jim8y merged commit b2feec5 into neo-project:master Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants