[SalesForce] Lightning – ‘delete’ button

JavaScript buttons don't work the way you expect, and I'm pretty sure that the code you're trying to use won't work. That said, you have an alternative you can use (tested/verified).

First, create a new Apex Class:

public class CaseAcceptOwnership {
    PageReference cancel;
    Case[] records;
    public CaseAcceptOwnership(ApexPages.StandardSetController c) {
        records = (Case[])c.getSelected();
        cancel = c.cancel();
    }
    public PageReference updateCases() {
        for(Case record: records) {
            record.OwnerId = UserInfo.getUserId();
        }
        update records;
        return cancel.setRedirect(true);
    }
}

Next, create a Visualforce page:

<apex:page standardController="Case" recordSetVar="cases" extensions="CaseAcceptOwnership" action="{!updateCases}">
</apex:page>

After that, go to Setup > Customize > Cases > Buttons, Links, and Actions, and create a new List Button (with select checkboxes), choose Visualforce for the Content Source, and choose the new page you created.

Finally, go ahead and add this button to your Search Layout, and you're done. The user can select records, and when they click the button, they will own the selected cases. You may want to add some error handling or something, but this should get you started.

Edit: Example Unit Test

Again, does not cover failure conditions, so make sure you add additional error handling if there's a possibility of failure.

@isTest class CaseAcceptOwnershipTest {
    @isTest public static void test() {
        // Get All Fields
        String[] fields = new List<String>(sObjectType.User.fields.getMap().keySet());
        // Get Test User Data
        Id userId = UserInfo.getUserId();
        User tempUser = Database.query('select '+String.join(fields,',')+' from user where Id = :userId');
        // Clone and clear out problematic fields
        tempUser = tempUser.clone(false, false, false);
        tempUser.FederationIdentifier = null;
        tempUser.Alias = 'testUser';
        tempUser.CommunityNickname = 'testUser';
        tempUser.UserName = 'testUser'+Math.random()+'@not-a-real-domain.or-tld';
        
        // This automatically does a DML, saves us one. Also avoids MIXED_DML errors.
        System.runAs(tempUser) {
            Account accountRecord = new Account(Name='Test');
            Contact contactRecord = new Contact(LastName='Test');
            Case caseRecord = new Case(Subject='Test',Status='Open', OwnerId=tempUser.Id);
            // Multi-Object insert for performance
            insert new sObject[] { accountRecord, contactRecord, caseRecord };
    
            contactRecord.AccountId = accountRecord.Id;
            caseRecord.ContactId = contactRecord.Id;
            caseRecord.AccountId = accountRecord.Id;
            // Assocate records together
            update new sObject[] { contactRecord, caseRecord };
        }
        Test.startTest();
        // Instantiate controller as it would be from the Visualforce page
        ApexPages.StandardSetController standardSetController = new ApexPages.StandardSetController([
            select id from case
        ]);
        standardSetController.setSelected(standardSetController.getRecords());
        // And the extension controller
        CaseAcceptOwnership controller = new CaseAcceptOwnership(standardSetController);
        // Avoid MIXED_DML error, run as yourself
        System.runAs(new User(Id=UserInfo.getUserId())) {
            ApexPages.PageReference result = controller.updateCases();
        }
        Test.stopTest();
        // Verify ownership change
        System.assertEquals(1, [SELECT COUNT() FROM Case WHERE OwnerId = :UserInfo.getUserId()]);
    }
}

You need to add the Google Info custom button from the Salesforce1 & Lightning Actions bucket to the Salesforce1 & Lightning Actions section in the layout for it to appear in the Lightning Experience view of the page.

If you just move it to the Custom Buttons section (bottom part of the above screenshot), it shows in Salesforce classic view only.

In your screenshot, you added the button to the Detail page, so it shows in Classic only. Add the button to the Salesforce1 and Lightning Experience Actions section just above it.