You're welcome!

I will plan on this Venu

Waiting

I will do a session on this Nitin

I will plan Ranjeet

Hi Esen Both SDET (Software Development Engineer in Test) and DevOps are valuable career paths in the IT industry, and the choice depends on your interests and career goals. Here are some factors to consider: 1. Skill Set: SDET focuses on software testing, automation, and quality assurance. If you enjoy working with testing frameworks, writing test scripts, and ensuring software quality, SDET can be a good fit for you. On the other hand, DevOps involves a broader set of skills, including infrastructure automation, continuous integration and deployment, configuration management, and monitoring. If you have a passion for infrastructure management, deployment pipelines, and ensuring efficient software delivery, DevOps might be the right choice. 2. Career Opportunities: Both SDET and DevOps roles have good career prospects. SDETs are in demand for their expertise in testing and automation, especially with the growing adoption of Agile and DevOps practices. DevOps professionals are sought after for their skills in streamlining software delivery processes, improving collaboration between development and operations teams, and optimizing infrastructure. Assess the job market in your area and consider which role aligns better with the opportunities available. 3. Personal Interests: Consider your personal interests and preferences. If you enjoy working closely with developers, writing code, and focusing on the quality aspects of software development, SDET can be a rewarding career choice. If you have an affinity for infrastructure, cloud technologies, and optimizing software delivery pipelines, DevOps might be a better fit. It's important to choose a career path that aligns with your interests and motivates you. 4. Learning Curve: Both SDET and DevOps roles require continuous learning and keeping up with industry trends and technologies. Assess your learning capacity and determine which path you feel more comfortable starting with. If you already have some experience in AWS and cloud technologies, you might find it easier to build on that knowledge and continue pursuing DevOps. On the other hand, if you feel more confident in your testing and quality assurance skills, starting with SDET can provide a strong foundation. Ultimately, there is no right or wrong answer. Both SDET and DevOps offer promising career paths. Consider your interests, skills, and long-term goals, and choose the path that excites you the most. It's also worth noting that the SDET and DevOps domains can overlap, and you can transition between the two roles over time with the right skill development and experience.

@@RaghavPal Thank you so much for the clarification sir!!! Much appreciated!

I will do Bereket

Hi, you can go with that, I will say API Automation testing along with some CI CD tools will be good for you

@@RaghavPal Thank you so much sir

Nikesh Software Engineer in Test (SET) and Software Development Engineer in Test (SDET) are both roles involved in software testing, but they have different responsibilities and skillsets. *Software Engineer in Test (SET)* A SET is responsible for designing, developing, and executing automated tests. They have a strong background in software development and testing methodologies, and they are proficient in using testing tools and frameworks. SETs work closely with developers to ensure that software meets quality standards. *Responsibilities of a SET:* * Design and develop automated test cases * Execute automated test cases * Analyze test results and identify defects * Report defects to developers * Maintain and update test automation frameworks *SDET* An SDET is a hybrid role that combines the skills of a software developer and a tester. SDETs are responsible for designing, developing, and executing both manual and automated tests. They have a strong understanding of the software development process and are able to identify and resolve defects early in the development cycle. SDETs work closely with developers to ensure that software is designed and implemented in a testable way. *Responsibilities of an SDET:* * Design and develop manual and automated test cases * Execute manual and automated test cases * Analyze test results and identify defects * Report defects to developers * Maintain and update test automation frameworks * Develop and implement testability strategies * Review code for testability *Key Differences Between SET and SDET* *Focus:* SETs focus on automated testing, while SDETs focus on both manual and automated testing. *Skills:* SETs have a strong background in software development and testing methodologies, while SDETs have a strong understanding of the software development process. *Role:* SETs are typically testers who collaborate with developers, while SDETs are hybrid roles that combine the skills of developers and testers. *Which Role is Right for You?* The best role for you will depend on your skills and interests. If you are interested in software development and want to focus on automated testing, then a SET role may be a good fit for you. If you are interested in testing and want to work closely with developers to improve the quality of software, then an SDET role may be a better fit for you. I hope this helps

@@RaghavPal Sir since I generally used to watch your video's and learnt various things from you. Really the way you explained me is great. I'm getting destination of Software engineer in test in one good product based company. So I thought to ask from you previously I was working in MNC as a Automation tester. So according to you I got a good role am I right sir?.

That should be good. And in some time you will have more clarity and options

Most welcome Naveen

May not be very deep like a dev person, but must understand dev and programming

Hi Vinoth To transition into an SDET (Software Development Engineer in Test) role, here are some suggested next steps: 1. Develop Programming Skills: Since you already have experience with Selenium and Java, it's important to continue strengthening your programming skills. Consider learning additional programming languages such as Python or C#, as they are commonly used in automation and SDET roles. Also, focus on understanding concepts like data structures, algorithms, and object-oriented programming. 2. Expand Test Automation Knowledge: While Selenium is a widely used automation tool, there are other frameworks and tools that are popular in the industry. Familiarize yourself with different test automation frameworks and tools such as Appium for mobile testing, RestAssured for API testing, or JUnit and TestNG for unit testing. Broadening your skillset will make you more versatile and adaptable in different testing scenarios. 3. Learn Continuous Integration and Deployment (CI/CD): Gain knowledge and hands-on experience with CI/CD tools like Jenkins, GitLab CI, or Azure DevOps. Understand the concepts of continuous integration, automated builds, and deployment pipelines. SDET roles often involve integrating test automation into CI/CD processes to ensure timely and reliable software delivery. 4. Explore Test Infrastructure and Environments: As an SDET, you may be responsible for managing test infrastructure and test environments. Familiarize yourself with concepts like containerization (e.g., Docker), virtualization (e.g., VMware, VirtualBox), and cloud-based testing (e.g., AWS, Azure). Gain experience in setting up and configuring test environments to replicate production setups. 5. Enhance Test Design and Test Strategy Skills: SDETs are involved in designing effective test strategies and test plans. Focus on improving your skills in test design techniques, test case management, and test coverage analysis. Understand different testing methodologies like Agile, DevOps, and shift-left testing. Learn about risk-based testing and how to prioritize tests based on business impact 6. Gain Knowledge in Performance Testing and Security Testing: Expand your testing expertise beyond functional testing. Learn about performance testing tools like JMeter or Gatling to measure system performance under different loads. Additionally, understand the fundamentals of security testing, including concepts like penetration testing, vulnerability assessment, and secure coding practices 7. Develop Strong Communication and Collaboration Skills: SDET roles often involve working closely with development teams, product owners, and other stakeholders. Improve your communication and collaboration skills to effectively convey testing insights, collaborate on test automation frameworks, and advocate for quality practices within the development process 8. Stay Updated with Industry Trends: Keep up-to-date with the latest trends and advancements in the testing and automation space. Follow relevant blogs, join online communities, attend webinars, and participate in conferences or meetups to stay informed about emerging technologies and industry best practices Remember, transitioning to an SDET role is a journey that requires continuous learning and hands-on experience. Consider taking up relevant projects or contributing to open-source projects to showcase your skills and build a strong portfolio. Networking with professionals in the field and seeking mentorship opportunities can also be beneficial for your career progression

@@RaghavPal Thanks Raghav for the detailed information!! 👍👍

Yash Whether a commerce background with seven years of experience can take the risk to do a course and learn SDET and move to that profession depends on several factors, but it can be a great career move with the right approach and preparation. Here's a breakdown of the pros and cons to help you decide: Pros: High demand for SDETs: The demand for skilled SDETs is rapidly growing, especially in e-commerce, as companies increasingly rely on software applications. This means you'll have good job prospects with your commerce background and newly acquired SDET skills. Lucrative salaries: SDETs typically earn competitive salaries, often higher than many commerce roles. With your experience, you can potentially command an even higher salary. Challenging and rewarding work: SDET work is intellectually stimulating and involves problem-solving, critical thinking, and staying ahead of the curve with new technologies. It can be very rewarding to contribute to building and testing high-quality software. Transferable skills: Many of the skills you've learned in your commerce background, such as communication, analysis, and attention to detail, are valuable in SDET roles. This makes the transition smoother and leverages your existing expertise. Cons: Initial learning curve: The transition from commerce to SDET will involve learning new programming languages, testing frameworks, and software development methodologies. This can be challenging, especially if you don't have a strong technical background. Career change risk: Leaving a stable career in commerce for a new field like SDET involves some risk. However, with the right skills and preparation, the potential rewards can outweigh the risks. Competitive job market: While the demand for SDETs is high, the job market can still be competitive. Make sure you have a strong portfolio and demonstrate your skills effectively to stand out. Here are some additional tips to increase your chances of success: Choose the right course: Select a reputable SDET course that covers the essential skills and tools needed for the job. Look for courses with practical hands-on learning and career guidance. Network with SDETs: Connect with experienced SDETs through online communities or professional networking events. They can provide valuable insights and mentorship. Build your portfolio: Start working on personal projects or contribute to open-source projects to gain practical experience and showcase your skills to potential employers. Highlight your transferable skills: When applying for SDET jobs, emphasize how your commerce background skills, such as communication, analysis, and problem-solving, can be valuable in an SDET role. Overall, moving from a commerce background to SDET can be a rewarding career change with the right preparation and determination. If you're passionate about technology and enjoy challenges, it's definitely worth considering. Remember, the initial learning curve is an investment in your future, and the potential rewards are significant. Here are some additional resources that you may find helpful: Software Development Engineer in Test (SDET) career path: [fullstackqe.org/career-roadmap-for-sdet-automation/](fullstackqe.org/career-roadmap-for-sdet-automation/) 5 Tips for Transitioning from Non-Technical to SDET: [www.techtorialacademy.com/apply-now](www.techtorialacademy.com/apply-now) How to Become an SDET with No Programming Experience: [www.reddit.com/r/LocalLLaMA/comments/13mwupt/lambdalabs_offering_free_compute_for_30_days_to/](www.reddit.com/r/LocalLLaMA/comments/13mwupt/lambdalabs_offering_free_compute_for_30_days_to/) I hope this information helps you make an informed decision about your career path..

I am not aware of that

Aditya Let me provide some insights to help you decide between Software Testing and SDET (Software Development Engineer in Test). 1. Software Testing: - Role: Software testers focus on assessing software applications manually. They verify whether the application behaves as expected based on specifications. - Responsibilities: - Execute test cases. - Identify defects. - Validate functionality. - Perform exploratory testing. - Skills Needed: - Attention to detail. - Analytical thinking. - Good communication. - Understanding of software requirements. - Career Path: - Manual testers can progress to senior testing roles or specialize in specific domains (e.g., security testing, performance testing). 2. SDET (Software Development Engineer in Test): - Role: SDETs bridge the gap between development and testing. They combine quality engineering with software development. - Responsibilities: - Write and integrate test code into the development process. - Create test automation tools. - Understand both black box and white box testing techniques. - Validate functional and non-functional aspects. - Skills Needed: - Coding skills (often in languages like Java, Python, or C#). - Knowledge of testing frameworks and tools. - Understanding of software architecture. - Ability to design and implement automated tests. - Career Path: - SDETs can advance to senior roles, such as test architects or quality leads. - They may also transition into development roles if desired. 3. Which One to Choose? - If you enjoy manual testing, have good attention to detail, and prefer a functional testing focus, consider software testing. - If you're interested in automation, coding, and want to work closely with developers, SDET might be a better fit. Remember that both paths have their merits, and your choice should align with your interests and long-term goals. Consider exploring both areas to see which resonates with you more. -

DevOps will be a better option

@@RaghavPal thank you sir. I AM confused which field I need to choose right now .I have intrest in docker,kubernetes and testing.Also i have learnt jmeter through your channel.

Automation related fields will be good

No, knowing only core Java won't be enough for most SDET roles. While a strong foundation in core Java is essential, modern SDET roles require additional skills and tools: Technical Skills: Testing Frameworks: Learn frameworks like JUnit, Selenium WebDriver, Appium, or Cypress. Test Automation Tools: Familiarity with automation tools like Cucumber, Robot Framework, or BDD frameworks is valuable. API Testing: Understanding API concepts and tools like Postman or RestAssured is increasingly important. Version Control Systems: Familiarity with Git or other version control systems is crucial for collaboration. Scripting Languages: Knowledge of scripting languages like Python, Groovy, or JavaScript can be advantageous for automation tasks. Database Concepts: Basic understanding of databases and SQL helps interpret test data and troubleshoot issues. Soft Skills: Problem-solving: Identify, analyze, and fix bugs effectively. Communication: Collaborate effectively with developers, QA teams, and stakeholders. Analytical Thinking: Understand test outcomes and analyze their implications. Attention to Detail: Meticulously identify and report bugs. Adaptability: Embrace new technologies and learn quickly. Getting Started: Online Courses: Take online courses or tutorials on SDET skills. Personal Projects: Build personal projects to showcase your skills and understanding. Open Source Contributions: Contribute to open-source projects to gain practical experience. Networking: Connect with other SDETs and professionals for guidance and opportunities. While core Java is important, being an SDET involves a broader skillset. Focus on continuous learning, acquiring relevant skills, and building a strong portfolio to improve your chances of success in this exciting field. Remember, learning never stops in the tech industry. Embrace the challenge, be persistent, and you can definitely thrive as an SDET

Yes, you can

How to become an SDET ...?

@@AnjanPrasad selenium knowledge Api testing both postman rest assured Testing basics/concepts revise over n over Data structures about 200 quality problems to recognise patterns 2 min projects in testing Good knowledge of oops in java/python/c++

Hi Shahul, As discussed in this video SDET is like a bridge between Dev, QA, Operations, & all teams. So they will be expected to understand dev and programming

No Ramu, but I have some courses there

Not yet Vini

No Pooja, can check all topics here - automationstepbystep.com/

Hi Nikka, In the context of software or technology, a "vanilla setup" usually means a basic installation or configuration without any customizations or modifications. For example, a vanilla setup of an operating system or a software application refers to the default installation with no additional programs or settings installed.

QA Engineer works within the QA team with the following roles: Test Planning Scenarios prep Test Execution Reporting Bugs Follow ups Automation planning Automation frameworks etc

@@RaghavPal sir developer apply to this job or not