Skip to main content

Weekend Testing Europe - Testing Session for LinkedIn

Great time had during Weekend Testing Europe, recommended for all to sharpen up your skills, ask questions, or just get a bit of practice. The exercise in principle was compare features from mobile to desktop on the beautiful LinkedIn app/site...

For those interested my testing session files generated:

-----------------------------------------------------------------------------------------------------------------------

Linked In Mobile App

iPhone 5s iOS 8.3

Search Functionality

Risks:
## No access to search algorithm to verify results

Start:

##User needs to authenticate for search function to be available.

Flow:

##On tapping search and entering no details, contacts appear alphabetically ascending.
##Cancelling returns to home tab and reloads the Newsfeed.
##Options for the user:
People
Contacts appear alphabetically ascending.
Jobs
Displays a set of jobs you may be interested in 
? Unknown algorithm for this, would need to be verified ?
Displays option to set location
In a new dialog you can search for a location or use current
Using current prompts for access to location services
Don't allow and the screen goes blank you can only cancel.
App remembers that you have disallowed location use.
Companies
Displays the companies you are currently following
? What happens when you follow no companies ?
Groups
Displays your currently joined groups
? What happens when you have no groups ?
## Search
People 
Adding search terms filters your own contacts first, then returns those you may know
? Unverified algo here ?
TO CHECK - Searching on a full name of a contact you already have returns those you don't only
Can search with only 1 char -  hopefully this is managed in the search algo
Jobs
TO CHECK - Cannot search by company, only title
Title appears to be fuzzily matched, without location set you get jobs from all over.
With location set:
Latest jobs are returned first, lots of jobs in Leeds.
Location can be removed, returns to previous results.
Job title and location can be used in conjunction. 

-----------------------------------------------------------------------------------------------------------------------

LinkedIn Desktop

Windows 8.1, Chrome 42

Search Functionality

##Risks:
Again, no understanding of the search algo
Should be aware that the aim is different here than the mobile experience, search for power and results rather than speed.

##Start:
User does not need to be authenticated to search
Minor functionality is available, searching by first name and last name
The search is a true 'elastic search' rather than the linear, categorised search.

##Search
Entering text exposes:
People
Companies
Showcased Pages
Groups
Universities
Features
Can search with 1 char - 18 results are filtered each time.
The 18 results are shared between the above categories
The search dynamically filters as you type.
Searching on a full name reliabily returns connected and unconnected users  (mobile app only unconnected users)
Company search defaults three options
Jobs
Those who work there
Those who no longer work there
Typing a search terms and the clicking search opens a new page with advanced search options

-----------------------------------------------------------------------------------------------------------------------

Summary

-Desktop was a true elastic search, built for power with a dependable connection, mobile much more category dependant and about returning immediate results
-Desktop was much more powerful, but both filtered and gave suggestions as you entered data. Mobile good for filtering what you already have, desktop better for finding new stuff.

-----------------------------------------------------------------------------------------------------------------------

If you haven't already, get yourselves signed up for next time:

http://weekendtesting.com/

Comments

Popular posts from this blog

Wheel of Testing Part 2 - Content

Thank you Reddit, while attempting to find pictures of the earths core, you surpass yourself.
Turns out Steve Buscemi is the centre of the world.

Anyway. Lets start with something I hold to be true. My testing career is mine to shape, it has many influences but only one driver. No one will do it for me. Organisations that offer a career (or even a vocation) are offering something that is not theirs to give. Too much of their own needs get in the way, plus morphing into a badass question-asker, assumption-challenger, claim-demolisher and illusion-breaker is a bit terrifying for most organisations. Therefore, I hope the wheel is a tool for possibilities not definitive answers, otherwise it would just be another tool trying to provide a path which is yours to define.


In part one, I discussed why I had thought about the wheel of testing in terms of my own motivations for creating it, plus applying the reasoning of a career in testing to it. As in, coming up with a sensible reflection of real…

Getting started with testability

At TestBash Netherlands, I said that, in my experience, a lot of testers don't really get testability. I would feel bad if I didn't follow that up with a starting point for expanding your mindset and explicitly thinking about testability day to day, and making your testing lives better! 

In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.
Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you! 

Overall Model:

Heuristics of Software Testability by James Bach

http://www.satisfice.com/tool…

The Team Test for Testability

You know what I see quite a lot. Really long-winded test maturity models. 

You know what I love to see? Really fast, meaningful ways to build a picture of your teams current state and provoke a conversation about improvement. The excellent test improvement card game by Huib Schoots and Joep Schuurkes is a great example. I also really like 'The Joel Test' by Joel Spolsky, a number of questions you can answer yes or no to to gain insight into their effectiveness as a software development team.

I thought something like this for testability might an interesting experiment, so here goes:

If you ask the team to change their codebase do they react positively?Does each member of the team have access to the system source control?Does the team know which parts of the codebase are subject to the most change?Does the team collaborate regularly with teams that maintain their dependencies?Does the team have regular contact with the users of the system?Can you set your system into a given state…