# How To Create A Plan For Solving A Problem Using Phoenix Checklist Thinking Tool — Tentamen Software Testing Blog

# TL;DR

In the last post, we presented a CIA thinking tool called The Phoenix Checklist. We used it to identify the real problem with the Google Page Rank feature. Today we create a plan for solving that problem. Many thanks to Marcel, who sublimed this great resource on his blog, That’s the buffet table.

How to create a plan for solving the How To Fake Google Page Rank problem using the Phoenix Checklist? Phoenix Checklist gave us a list of questions to identify what is an actual problem that we want to solve. To create a plan to solve that problem, the Phoenix Checklist contains 22 questions.

# The Problem

How To Fake Google Page Rank?

# The Plan

Can you solve the whole problem? Part of the problem?

First, we need to break the problem into smaller parts. As the PageRank algorithm has many variables, this could be the strategy for braking the problem. There are hidden parts of this algorithm, so it is unlikely to solve the whole problem. But part of the problem could be solved.

What would you like the resolution to be?

An application that would automatically “insert” into Internet fake PageRank for the desired domain.

How much of the unknown can you determine?

PageRank algorithm has many resources, but some are still hidden by Google. We can guess that 90% of the algorithm is publicly available.

Can you derive something useful from the information you have?

Yes. We can conclude what should be done on other domain pages to get higher Page Ranks for the targeted domain.

Have you used all the information?

Have you taken into account all essential notions in the problem?

Can you separate the steps in the problem-solving process? Can you determine the correctness of each step?

Those three questions are checkboxes for a proposed process that develops the solution.

What creative thinking techniques can you use to generate ideas? How many different techniques?

Phoenix Checklist is just one of the thinking tools.

Can you see the result? How many different kinds of results can you see?

Testing the solution is the hard problem. As there is no available Google staging environment, we can only test in production. It takes some time to see the production result after running the prototype solution because Google crawlers take time to do their work.

How many different ways have you tried to solve the problem?

We should try several PageRank algorithm definitions.

What have others done?

Papers on PageRank algorithm.

Can you intuit the solution? Can you check the result?

Testing in production is hard but possible.

What should be done? How should it be done?

As application.

Where should it be done?

When should it be done?

Who should do it?

What do you need to do at this time?

Who will be responsible for what?

Those questions help us to set the Project Team.

Can you use this problem to solve some other problem?

We should try it on other popular search engines.

What are the unique set of qualities that makes this problem what it is and none other?

It is tough to fake page rank results. The algorithm is using data from the Internet, making it a network theory problem and very expensive if we want to try a brute force solution.

What milestones can best mark your progress?

Our toolsets for domain top 100-page rank.

How will you know when you are successful?

Faked Page rank results are shown in two days.

# Conclusion

Here we get to the list of excellent thinking tools. Remember that software testing is always a solving problem.

*Originally published at **https://blog.tentamen.eu** on January 20, 2021.*