Sounds liek you don't have a grasp of what the differences are. These concepts are not unique to Apex. A list is an ordered sequence of items, like people waiting to get their number called. The thing is, one person can have more than one number assigned, so they can appear in the waiting list more than once. A set is almost like a list except it does not allow for a person to have more than one chance to be in the waiting list (so it only appears once on the whole waiting list) and it's not ordered, so doesn't matter what number the person got assigned to it. A map is a representation of the person waiting and it's number. That number is unique, so it's the key, the person assigned to the number is the value, so each entry of the map is a pair where you can't have two pairs with the same key. Where does it all make sense to use? Well, it depends on the use case. Let's say you want to check all the accounts of all the opportunities to get the account type, the account ID, the name and the opportunity Id and Opp name and export it to a csv so someone somewhere can analyze it. You do your SOQL query, get everything in a nice list and you output it into a nice excel sheet with a pretty header, mail it to the guy that requested it. You come up with this little piece of code: List lstOpp = [Select Id, AccountId, Account.Type from Opportunity]; String output = ''; for(Opportunity opp : lstOpp){ output+=opp.Id+','; output+=opp.AccountId+','; output+=opp.Account.Type+'\n'; } system.debug(output); A day later he replies: "hey! I'm noob at excel and there's duplicates here I don't know how to get rid of. Can you just send it to me without duplicates? Thanks!" You then think: Ok, I'll just add the Opportunities I get from the query and put it into a Set! That way, they get the information they want and no duplicates, right? Right!? Let's see... List lstopp = [Select Id, AccountId, Account.Type from Opportunity]; String output = ''; Set stOpp = new Set(); for(Opportunity opp : lstopp){ stOpp.add(opp); } for(Opportunity opp : stOpp){ output+=opp.Id+','; output+=opp.AccountId+','; output+=opp.Account.Type+'\n'; } system.debug(output); That't not right! My unique value is an opportunity... What I need is to have something that allows me to check if a certain Account is already added on the list I'm writting down on the CSV. Let's however see how this can be done by throwing a Map into the mix :) List lstopp = [Select Id, AccountId, Account.Type from Opportunity]; String output = ''; Map mapOppsByAccountId = new Map(); for(Opportunity opp : lstopp){ /* Notice what happens if you put the same key twice: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_methods_system_map.htm#apex_methods_system_map */ mapOppsByAccountId.put(opp.AccountId,opp); } for(Id accountId : mapOppsByAccountId.keySet()){ Opportunity opp = mapOppsByAccountId.get(accountId); output+=opp.Id+','; output+=opp.AccountId+','; output+=opp.Account.Type+'\n'; } system.debug(output); Not the best example but I think it helps. If you have more questions (or if I made it even more complicated) let me know. More on reddit.com

I saw that there were some changes related to unit test logic in latest release (https://github.com/forcedotcom/salesforcedx-vscode/pull/2961) and it seems like the SF team is already aware of the issues, (see comments here https://github.com/forcedotcom/salesforcedx-vscode/issues/2981) but I didn't see any issue like Yours created in Github issues. I'd suggest You to create one, this is the fastest way to get it fixed

More on reddit.com

Spent around an hour trying to find the key, assumed I was missing something. The region wasn't connected lol More on reddit.com

How are you able to host custom matches with only 1 team?

More on reddit.com