Skip to main content

Data Analysis + Automation Testing 12-week starter study plan

 

🔹 Step 1: Foundation (Weeks 1–4)

Focus on core building blocks that overlap both fields.

Week 1–2: Excel + Git basics

  • Excel: Formulas, Pivot Tables, Charts, Filtering, Conditional Formatting.

  • Git: init, clone, add, commit, push, pull, branching basics.

  • Small project: Create a mini sales dashboard in Excel and upload it to GitHub.

Week 3–4: Python (basics)

  • Python: Variables, loops, functions, data structures (lists, dicts).

  • Libraries: pandas (basic data analysis), matplotlib (basic plotting).

  • Small project: Load a CSV in pandas, clean it, and plot graphs. Push code to GitHub.

🔹 Step 2: Specialized Tracks (Weeks 5–10)

Now split time between Data Analysis and QA Automation.

Week 5–6: SQL + JavaScript basics

  • SQL: SELECT, WHERE, JOIN, GROUP BY, ORDER BY. Practice on sample databases.

  • JS: Variables, arrays, objects, functions, loops.

  • Mini-projects:

    • Write SQL queries for a mock e-commerce DB.

    • JS program that manipulates arrays (e.g., filter products > $50).

Week 7–8: Tableau + TypeScript

  • Tableau: Import CSV, build dashboards, use calculated fields.

  • TypeScript: Types, interfaces, functions, error handling.

  • Mini-project:

    • Build a Tableau dashboard from SQL-exported data.

    • Rewrite your JS array project in TypeScript.

Week 9–10: Playwright + Jest (Automation Testing)

  • Playwright: Browser automation, selectors, assertions.

  • Jest: Unit testing basics (describe, it, expect).

  • Mini-project:

    • Write Jest tests for a small JS function.

    • Write Playwright tests to check login flow on a demo website.

🔹 Step 3: Integration & Projects (Weeks 11–12)

Bring everything together.

  • Data Analyst project: Combine SQL + Python + Tableau → end-to-end report.

  • QA Automation project: Automate test cases for a sample web app (with Git version control).

  • Document your projects on GitHub/LinkedIn.

📌 Weekly Time Split Suggestion (if ~1 hr/day = 7 hrs/week)

  • 3 hrs → Current focus topic (Excel → Python → SQL → etc.)

  • 2 hrs → Review + practice past topics.

  • 1 hr → Mini-project work.

  • 1 hr → Git & documentation.

✅ With this, you’ll:

  • Build skills step by step without burning out.

  • Have small projects to show for each tool.

  • Cover both Data Analysis and Automation Testing in parallel.


Perfect! Let’s make this super practical and trackable 🚀
I’ll give you a Week 1 daily plan (7 days, 1 hr/day) where you’ll cover Excel + Git basics. Each day has one clear task.

You can literally copy-paste this into your Blogger site and check off once done ✅.

📅 Week 1 Study Plan (Excel + Git Basics)

Goal: Get comfortable with Excel for analysis and start tracking code with Git.

Day 1 – Excel Basics

⏱️ 1 hr

  • Learn: Cell references (A1 vs $A$1), basic formulas (SUM, AVERAGE, MIN, MAX).

  • Task: Create a sheet with 10 products, their price, and quantity. Calculate total revenue per product.

Day 2 – Excel Formatting & Filters

⏱️ 1 hr

  • Learn: Sorting, filtering, conditional formatting.

  • Task: Apply filters to show only products with revenue > 500. Highlight them in green.

Day 3 – Excel Pivot Tables

⏱️ 1 hr

  • Learn: Create a pivot table (summarize revenue by category).

  • Task: Add a pivot chart to visualize category revenue.

Day 4 – Excel Mini-Project

⏱️ 1 hr

  • Task: Build a small Sales Dashboard (summary table + chart).

  • Bonus: Use slicers for filtering.

  • Save your Excel file as week1_sales_dashboard.xlsx.

Day 5 – Git Setup & Basics

⏱️ 1 hr

  • Install Git (if not installed).

  • Learn: git init, git status, git add, git commit.

  • Task: Create a folder study-tracker, add a text file week1_notes.txt, commit it.

Day 6 – GitHub & Push

⏱️ 1 hr

  • Learn: Create a GitHub repo, connect local → remote.

  • Commands: git remote add origin, git push -u origin main.

  • Task: Push your week1_sales_dashboard.xlsx + week1_notes.txt to GitHub.

Day 7 – Weekly Review & Documentation

⏱️ 1 hr

  • Review what you learned in Excel + Git.

  • Task: Write a short blog post / notes file:

    • 3 Excel things you learned

    • 3 Git commands you used

  • Commit & push this reflection file to GitHub.

👉 By end of Week 1:

  • You’ll have 1 Excel dashboard.

  • A GitHub repo with your work.

  • A habit of tracking progress daily.

Comments

Post a Comment

Popular posts from this blog

30 Manual Testing interview questions from glass door

Here are 30 manual testing interview questions commonly encountered in interviews, compiled from various sources including Glassdoor: What is the difference between Quality Assurance (QA), Quality Control (QC), and Software Testing? QA focuses on improving the processes to deliver Quality Products. QC involves the activities that ensure the verification of a developed product. Software Testing is the process of evaluating a system to identify any gaps, errors, or missing requirements. Can you explain the Software Testing Life Cycle (STLC)? The STLC includes phases such as Requirement Analysis, Test Planning, Test Case Development, Environment Setup, Test Execution, and Test Closure. What is the difference between Smoke Testing and Sanity Testing? Smoke Testing is a preliminary test to check the basic functionality of the application. Sanity Testing is a subset of regression testing to verify that a specific section of the application is still worki...
Post a Comment
Read more

Part 1-Interview questions for Manual testing

1. What is Software Testing? Answer: Software testing is the process of evaluating a software application to identify any discrepancies between expected and actual outcomes, ensuring the product is defect-free and meets user requirements. ​ GUVI 2. What are the different types of Software Testing? Answer: The main types include: ​ Software Testing Material +1 LinkedIn +1 Functional Testing: Validates the software against functional requirements. ​ Non-Functional Testing: Assesses aspects like performance, usability, and reliability. ​ Manual Testing: Test cases are executed manually without automation tools. ​ Software Testing Material +2 LinkedIn +2 Katalon Test Automation +2 Automation Testing: Utilizes scripts and tools to perform tests automatically. ​ 3. What is the difference between Verification and Validation? Answer: Verification: Ensures the product is designed correctly, focusing on processes and methodologies. ​ Validation: Ensures the bui...
Post a Comment
Read more

1000 Interview questions part 1

Test Case Design – Interview Questions & Answers (1–50) 1. What is a test case? A test case is a set of actions executed to verify a particular feature or functionality of your application. 2. What are the components of a test case? Test case ID, Description, Preconditions, Steps, Test Data, Expected Result, Actual Result, Status, Comments. 3. What is test case design? It's the process of creating a set of inputs, execution conditions, and expected results to verify if the system meets requirements. 4. Why is test case design important? It ensures effective testing coverage, reduces testing time, and helps find more defects. 5. Name some common test case design techniques. Equivalence Partitioning, Boundary Value Analysis, Decision Table Testing, State Transition Testing, Error Guessing, Use Case Testing. 6. What is Equivalence Partitioning? A technique that divides input data into valid and invalid partitions to reduce the number of test cases. 7. Give an example...
Post a Comment
Read more