root
/
jenkins
mirror of https://github.com/jenkinsci/jenkins.git
1
0
Fork 0
Code Issues Actions 12 Packages Projects Releases Wiki Activity

start introducing data-testids for test usage 

The Header rework exposed numerous test failures due to changes in structure.  
This could have been avoided if we had already been using data-testid attributes for the various things.

This starts small with the signin button.

Using "login" as the testid as this is what cloudbees had already been using in our custom header and the jelly is still loginLink
This commit is contained in:
James Nord 2025-06-20 17:41:01 +01:00 committed by GitHub
parent 15caec2907
commit a81cab9717
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
core/src/main/resources/hudson/security/SecurityRealm/loginLink.jelly
View File

@ -27,6 +27,7 @@ THE SOFTWARE.
<j:jelly xmlns:j="jelly:core">
<a class="jenkins-button"
data-type="header-action"
data-testid="login"
href="${rootURL}/${app.securityRealm.loginUrl}?from=${app.securityRealm.from}"
style="aspect-ratio: unset; padding: 0.5rem 1rem"
tooltip="${%signInTooltip}">