Hannah.Nguyen

Version control, also known as source control, is the practice of tracking and managing changes to software code. Version control systems are software tools that help software teams manage changes to source code over time. As development environments have accelerated, version control systems help software teams work faster and smarter. They are especially useful for  DevOps   teams since they help them to reduce development time and increase successful deployments. Version control software keeps track of every modification to the code in a special kind of database. If a mistake is made, developers can turn back the clock and compare earlier versions of the code to help fix the mistake while minimizing disruption to all team members. Benefits of version control systems 1. A complete long-term change history of every file. This means every change made by many individuals over the years. Changes include the creation and deletion of files as well as edits to their contents. Differ...

  1. Right-click the "Remotes" section header in the sidebar and select "Add Remote Repository". 2. In the dialog, you can enter a name (e.g. "origin") and the remote repo's URL on Github; additionally, you can select your GitHub account. 3. Confirm the dialog and the remote will now be connected to your local repository. 4. From now on, you can simply use the "Push" button in the toolbar to upload new changes to the remote on GitHub.

 Using Command line to PUSH to GitHub Creating a new repository.  Open your Git Bash.  Create your local project on your desktop directed towards a current working directory.  Add the file to the new local repository.  Add the URL copied, which is your remote repository to where your local content from your repository is pushed. Commit the files staged in your local repository by writing a commit message. Copy your remote repository's URL from GitHub. Add the URL copied, which is your remote repository to where your local content from your repository is pushed. Push the code into your local repository GitHub. View your files in your repository hosted on GitHub.

  Developers can follow these 10 steps to create a GitHub repository: Log into the GitHub administrative console Move to the GitHub Repositories page Click on the green “New” button Enter the name of the GitHub repository Include a description (optional) Choose to make this a public or private GitHub repository Add a README (optional) Include a .gitignore file for your development framework (optional) Choose a fair-use license Click the green “Create Repository” button to finish the process

GitHub is a web-based interface allowing real-time collaboration. It encourages teams to work together in developing code, building web pages, and updating content. GitHub is useful in the development stage for code, content, research, web pages, and more. With GitHub, users can easily track changes and navigate revisions.  GitHub allows users to create, store, change, merge, and collaborate on files or code. Any member of a team can access the GitHub repository (think of this as a folder for files) and see the most recent version in real time. Then, they can make edits or changes that the other collaborators also see. GitHub also lets users make requests of one another and internally discuss the iterations along the way. It’s even been called “a social coding platform” because it invites people to coordinate, share, and collaborate code across distributed and asynchronous environments.  

Scrum is an Agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices. Kanban is a visual system used to manage and keep track of work as it moves through a process. What are the differences between Scrum and Kanban? Scheduling:  In the Scrum approach, managers set sprints by determining clear deadlines for each aspect of the project. Kanban, on the other hand, encourages continuity with the responsibility of setting deadlines lying with the team leader. Duties:  In Scrum, every team member is delegated with a specific task. However, in Kanban, roles for team members are not strictly determined, resulting in greater cooperation. Improvisations:  Scrum does not really allow improvisations and changes in the middle of a sprint, while Kanban encourages modifications and promotes continuous adjustments. KPIs:  The velocity of a sprint helps in understanding productivity in Scrum. And s...

Scrum is a management framework that teams use to self-organise and work towards a common goal. In Scrum, i ncrements   of valuable work are delivered in short cycles of one month or less, which are called  s prints . Ongoing feedback occurs during the sprint, allowing for   inspection   and   adaptation   of the process and what will be delivered.  The scrum team has a  s crum master , a  p roduct owner   and  d evelopers , who are accountable for turning the selection of the work into an increment of value during a sprint. The scrum team and other members of their organization, business, users or stakeholders  inspect the results of the sprint and adjust for the next one. There are some benefits of using scrum: 1. Accelerate software quality 2. Enhance ability to manage changing priorities 3. Increase productivity 4. Improve business/IT alignment 5. Enhance software quality 6. Enhance delivery predictability 7. Reduce project...

A mind map is a simple way to visually structure your ideas to help with analysis and recall. It is generally used to organize information and make decisions. It can be used as a visual thinking tool for Agile teams.  Advantages of using mind maps: 1. Mind mapping helps to significantly improve test coverage. 2. Save time when creating test cases. 3. Mind maps are super easy to maintain and flexible to changing requirements (which is very important in Agile team). 4. Mind maps make standups and QA reporting sessions shorter and less painful because they are great communication tools. 

There are four main Agile ceremonies: the sprint planning meeting, the daily stand-up meeting, the sprint review meeting and the sprint retrospective meeting. 1. Sprint planning The sprint planning meeting is held at the beginning of the sprint and is where teams identify what can be delivered in the sprint and how that work will be achieved. At the end of the planning meeting, every scrum member needs to be clear on what can be delivered in the sprint and how the increment can be delivered. 2. Daily stand-up The daily stand-up is a 15-minute (or less) daily meeting to discuss progress and identify blockers. Attendees are urged to participate while standing to help keep the meeting short. 3. Sprint review The sprint review, also called an iteration review, is where the scrum team meets to reveal what was accomplished during the sprint. A development team shows which backlog items are “Done” to stakeholders and teammates, who can then give feedback. 4. Sprint retrospective A sp...

 There are at least 3 roles in Agile: product owner, scrum master and the development team. 1. The product owner: Setting clear direction Scrum product owners understand the customer and business requirements, and then create and manage the product backlog based on those requirements.  The Scrum Guide defines the product owner's responsibilities as: Managing the scrum backlog  Release management  Stakeholder management  2. The scrum master: Holding it all together The scrum master is the role responsible for gluing everything together and ensuring that scrum is being done well. They help the product owner define value, the development team deliver the value, and the scrum team to get better.  They serve the product owner by helping them better understand and communicate value, to manage the backlog, help them plan the work with the team, and break down that work to deliver the most effective learning. Serving the development team, the scrum master...

 Agile and Waterfall are 2 types of approach to project management. However, Agile is preferred because of the following reasons: 1. Flexibility and adaptability Agile is highly adapted to change, allowing for flexibility in requirements, priorities and project scope throughout the development project. This contrasts with Waterfall, which follows a linear, sequential approach and can struggle to accommodate changes once the project has started. 2. Iterative Development  With Agile approach, the project is broken into small, incremental iterations (sprints). It enables early and continuous feedback from stakeholders, leading to more accurate requirements and high-quality deliverables.  3. Customer Collaboration Customers can collaborate and engage throughout the development process. It ensures that the product meets customer expectations and delivers value. In Waterfall, the customer is less involved in the development process, increasing the risk of delivering a product t...

Waterfall is a project management method with a linear approach. In Waterfall, each stage of the workflow needs to be completed before moving on to the next step. Waterfall is suited for projects where the objectives are clearly outlined from the beginning. There are some disadvantages of Waterfall model: 1. Lack of Flexibility When it comes to creating software, the Waterfall Model is about as stiff and inflexible as it gets. It presumes that the design requirements are completely understood at the outset and that no alterations are necessary. This can be problematic if more requirements arise or if the design needs to be altered. Sometimes development process can take a long time and the requirements of clients can change or even new technology can outdate the current version of the software. The entire schedule can be thrown off if the project’s specifications are suddenly altered, rendering most of the work you’ve done up to that point meaningless. Hence, a lack of flexibility ...

DevOps is an evolving philosophy and framework that encourages faster, better application development and faster release of new or revised software features or products to customers. The practice of DevOps encourages smoother, continuous communication, collaboration, integration, visibility, and transparency between application development teams (Dev) and their IT operations team (Ops) counterparts. DevOps proponents describe several business and technical benefits, many of which can result in happier customers. Some benefits of DevOps include: Faster, better product delivery Faster issue resolution and reduced complexity Greater scalability and availability More stable operating environments Better resource utilization Greater automation Greater visibility into system outcomes Greater innovation

What is a compatibility test? Compatibility testing  is a type of testing that examines and compares  functionality over multiple browsers, devices, platforms, and OS to recognize potential discrepancies. Performing compatibility testing verifies that your product/software works efficiently in its intended environments. How is compatibility testing performed? 1. Identification of Target Environments: The first step is to identify the target environments for the software application. This includes different combinations of operating systems, hardware devices, browsers, network configurations, databases, and other relevant components. 2. Test Environment Setup : Test environments are set up to replicate the identified target configurations. This may involve setting up virtual machines, installing different operating systems and browsers, configuring network settings, and deploying the application on various platforms. 3. Test Case Design : Test cases are designed to cover t...

Unit testing is the process where you test the smallest functional unit of code. Software testing helps ensure code quality, and it's an integral part of software development. It's a software development best practice to write software as small, functional units then write a unit test for each code unit. You can first write unit tests as code. Then, run that test code automatically every time you make changes in the software code. This way, if a test fails, you can quickly isolate the area of the code that has the bug or error. Unit testing enforces modular thinking paradigms and improves test coverage and quality. Automated unit testing helps ensure you or your developers have more time to concentrate on coding.

Non-functional testing types: 1. Performance testing Performance testing is the practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size. . The process incorporates "performance" indicators such as browser, page, network response times, server request processing times, acceptable concurrent user volumes, processor memory consumption number, and type of error that might be encountered with the app. 2. Security testing Security testing is a type of software testing that uncovers vulnerabilities, threats, and risks in a software application and prevents malicious attacks from intruders. The purpose of security testing is to identify all possible loopholes and weaknesses of the software system that might result in a loss of information, revenue, or reputation at the hands of the employees or outside of the organization....

What is Black Box testing? In black-box testing, a tester doesn’t have any information about the internal working of the software system. Black box testing is a high level of testing that focuses on the behavior of the software. It involves testing from an external or end-user perspective. Black box testing can be applied to virtually every level of software testing: unit, integration, system, and acceptance. What is White Box testing? White-box testing is a testing technique which checks the internal functioning of the system. In this method, testing is based on coverage of code statements, branches, paths or conditions. White-Box testing is considered as low-level testing. It is also called glass box, transparent box, clear box or code base testing. The white-box Testing method assumes that the path of the logic in a unit or program is known. Black Box Testing Vs. White Box Testing In Black Box, testing is done without the knowledge of the internal structure of the program o...

Regression testing is a type of software testing conducted after a code update to ensure that the update introduced no new bugs. This is because new code may bring in new logic that conflicts with the existing code, leading to defects. Usually, QA teams have a series of regression test cases for important features that they will re-execute each time these code changes occur to save time and maximize test efficiency.   Smoke testing   is a software testing technique performed post software build to verify that the critical functionalities of software are working fine. It is executed before any detailed functional or regression tests are executed. The main purpose of smoke testing is to reject a software application with defects so that QA team does not waste time testing broken software applications. In smoke testing, the test cases chose to cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify ...

System Testing This is the level of testing that validates the complete and fully integrated software product. The purpose of a system test is to evaluate compliance with its specified requirements and specifications. Usually, the software is only one element of a larger computer-based system. Ultimately, the software is interfaced with other software/hardware systems. System Testing is actually a series of different tests whose sole purpose is to exercise the full computer-based system. System testing seeks to detect defects both within the “inter-assemblages” and also within the system as a whole. The actual result is the behaviour produced or observed when a component or system is tested. System testing is carried out to achieve the following: . Testing the fully integrated applications including external peripherals in order to check how components interact with one another and with the system as a whole. . Verify thorough testing of every input in the application to check for desi...