dotnet/runtime

Update naming conventions of HW intrinsics template based tests to avoid naming collisions

Open

#11,054 opened on Sep 7, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-CodeGen-coreclrhelp wantedtest-enhancement

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

Porting of increased number of HW intrinsic tests to template based hit the problem of test naming collision arising for several groups of tests. The solution to the problem could be based on using expanded test names and test file names composed from names of intrinsic function, vector types of return argument and one of operands, and names of base types of the vectors.

category:testing theme:hardware-intrinsics skill-level:beginner cost:small

Contributor guide

Research direction
Identify a group of HW intrinsic tests with naming collisions, then rename them following the proposed expanded naming convention (intrinsic function, vector types, base types).
Tech stack
csharp
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85