Tyagi Tour & Travels in Loni Ghaziabad

 Welcome to Tyagi Tour  & Travels:-

Welcome to Tyagi Tour & Travels in Loni Ghaziabad and NCR. These well-known establishments act as a one-stop destination servicing customers both local and from other parts of Delhi and NCR.

 

Satisfactions business employs individuals that are dedicated towards their respective roles and put in a lot of effort to achieve the common vision and larger goals of the company. In the near future, this business aims to expand its line of products and services and cater to a larger client base. In Delhi, this establishment occupies a prominent location in shanti nagar loni Ghaziabad. Categories: Car Hire, bus booking, online booking, Hotel booking, Flight booking, Railway booking, Money Transfer, Travelers on Hire, Tour Packages, Car Hire-Toyota Innova, bus booking Travelers on Hire for Outstation, 24*7 booking available. Car Hire, Car on Hire for Outstation-Toyota Innova, Mini Bus on Hire.

 

Owner and Founder: Mr. Mukesh Tyagi

 

Products and Services offered:-

 

Tyagi Tour & Travels in shanti nagar loni Ghaziabad has a wide range of products and services to cater to the varied requirements of their customers. The staff at this establishment is courteous and prompt at providing any assistance. They readily answer any queries or questions that you may have. Pay for the product or service with ease by using any of the available modes of payment, such as Cash. This establishment is functional from 00:00 - 23:59.

 

Please scroll to the top for the address and contact details of Tyagi Tour & Travels at Shani nagar Loni Ghaziabad and NCR.

 

Software Testing Basics :: Software Testing Interview Questions and Answers

1. 
   Can you explain the PDCA cycle and where testing fits in?
   Software testing is an important part of the software development process. In normal software development there are four important steps, also referred to, in short, as the PDCA (Plan, Do, Check, Act) cycle.
   
   Let's review the four steps in detail.
   1. Plan: Define the goal and the plan for achieving that goal.
   1. Do/Execute: Depending on the plan strategy decided during the plan stage we do execution accordingly in this phase.
   1. Check: Check/Test to ensure that we are moving according to plan and are getting the desired results.
   1. Act: During the check cycle, if any issues are there, then we take appropriate action accordingly and revise our plan again.
   
   So developers and other stakeholders of the project do the "planning and building," while testers do the check part of the cycle. Therefore, software testing is done in check part of the PDCA cyle.
   What is the difference between white box, black box, and gray box testing?
   Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested.
   White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
   There is one more type of testing called gray box testing. In this we look into the "box" being tested just long enough to understand how it has been implemented. Then we close up the box and use our knowledge to choose more effective black box tests.
   
   The above figure shows how both types of testers view an accounting application during testing. Black box testers view the basic accounting application. While during white box testing the tester knows the internal structure of the application. In most scenarios white box testing is done by developers as they know the internals of the application. In black box testing we check the overall functionality of the application while in white box testing we do code reviews, view the architecture, remove bad code practices, and do component level testing.
   Can you explain usability testing?
   Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer's perception and task time. The best way to finalize the customer point of view for usability is by using prototype or mock-up software during the initial stages. By giving the customer the prototype before the development start-up we confirm that we are not missing anything from the user point of view.
   
   What are the categories of defects?
   There are three main categories of defects:
   
   1. Wrong: The requirements have been implemented incorrectly. This defect is a variance from the given specification.
   1. Missing: There was a requirement given by the customer and it was not done. This is a variance from the specifications, an indication that a specification was not implemented, or a requirement of the customer was not noted properly.
   1. Extra: A requirement incorporated into the product that was not given by the end customer. This is always a variance from the specification, but may be an attribute desired by the user of the product. However, it is considered a defect because it's a variance from the existing requirements.
   How do you define a testing policy?
   The following are the important steps used to define a testing policy in general. But it can change according to your organization. Let's discuss in detail the steps of implementing a testing policy in an organization.
   
   • Definition: The first step any organization needs to do is define one unique definition for testing within the organization so that everyone is of the same mindset.
   • How to achieve: How are we going to achieve our objective? Is there going to be a testing committee, will there be compulsory test plans which need to be executed, etc?.
   • Evaluate: After testing is implemented in a project how do we evaluate it? Are we going to derive metrics of defects per phase, per programmer, etc. Finally, it's important to let everyone know how testing has added value to the project?.
   • Standards: Finally, what are the standards we want to achieve by testing? For instance, we can say that more than 20 defects per KLOC will be considered below standard and code review should be done for it.
   On what basis is the acceptance plan prepared?
   In any project the acceptance document is normally prepared using the following inputs. This can vary from company to company and from project to project.
   1. Requirement document: This document specifies what exactly is needed in the project from the customers perspective.
   1. Input from customer: This can be discussions, informal talks, emails, etc.
   1. Project plan: The project plan prepared by the project manager also serves as good input to finalize your acceptance test.
   
   The following diagram shows the most common inputs used to prepare acceptance test plans.
   
   What is configuration management?
   Configuration management is the detailed recording and updating of information for hardware and software components. When we say components we not only mean source code. It can be tracking of changes for software documents such as requirement, design, test cases, etc.
   When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.
   How does a coverage tool work?
   While doing testing on the actual product, the code coverage testing tool is run simultaneously. While the testing is going on, the code coverage tool monitors the executed statements of the source code. When the final testing is completed we get a complete report of the pending statements and also get the coverage percentage.
   
   Which is the best testing model?
   In real projects, tailored models are proven to be the best, because they share features from The Waterfall, Iterative, Evolutionary models, etc., and can fit into real life time projects. Tailored models are most productive and beneficial for many organizations. If it's a pure testing project, then the V model is the best.
   What is the difference between a defect and a failure?
   When a defect reaches the end customer it is called a failure and if the defect is detected internally and resolved it's called a defect.
   
   Should testing be done only after the build and execution phases are complete?
   In traditional testing methodology testing is always done after the build and execution phases.
   But that's a wrong way of thinking because the earlier we catch a defect, the more cost effective it is. For instance, fixing a defect in maintenance is ten times more costly than fixing it during execution.
   In the requirement phase we can verify if the requirements are met according to the customer needs. During design we can check whether the design document covers all the requirements. In this stage we can also generate rough functional data. We can also review the design document from the architecture and the correctness perspectives. In the build and execution phase we can execute unit test cases and generate structural and functional data. And finally comes the testing phase done in the traditional way. i.e., run the system test cases and see if the system works according to the requirements. During installation we need to see if the system is compatible with the software. Finally, during the maintenance phase when any fixes are made we can retest the fixes and follow the regression testing.
   Therefore, Testing should occur in conjunction with each phase of the software development.
   Are there more defects in the design phase or in the coding phase?
   The design phase is more error prone than the execution phase. One of the most frequent defects which occur during design is that the product does not cover the complete requirements of the customer. Second is wrong or bad architecture and technical decisions make the next phase, execution, more prone to defects. Because the design phase drives the execution phase it's the most critical phase to test. The testing of the design phase can be done by good review. On average, 60% of defects occur during design and 40% during the execution phase.
   
   What group of teams can do software testing?
   When it comes to testing everyone in the world can be involved right from the developer to the project manager to the customer. But below are different types of team groups which can be present in a project.
   • Isolated test team
   • Outsource - we can hire external testing resources and do testing for our project.
   • Inside test team
   • Developers as testers
   • QA/QC team.
   What impact ratings have you used in your projects?
   Normally, the impact ratings for defects are classified into three types:
    
   • Minor: Very low impact but does not affect operations on a large scale.
   • Major: Affects operations on a very large scale.
   • Critical: Brings the system to a halt and stops the show.
   Does an increase in testing always improve the project?
   No an increase in testing does not always mean improvement of the product, company, or project. In real test scenarios only 20% of test plans are critical from a business angle. Running those critical test plans will assure that the testing is properly done. The following graph explains the impact of under testing and over testing. If you under test a system the number of defects will increase, but if you over test a system your cost of testing will increase. Even if your defects come down your cost of testing has gone up.
   What's the relationship between environment reality and test phases?
   Environment reality becomes more important as test phases start moving ahead. For instance, during unit testing you need the environment to be partly real, but at the acceptance phase you should have a 100% real environment, or we can say it should be the actual real environment. The following graph shows how with every phase the environment reality should also increase and finally during acceptance it should be 100% real.
   
   What are different types of verifications?
   Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code. Types of verification are:
   1. Walkthrough: Walkthroughs are informal, initiated by the author of the s/w product to a colleague for assistance in locating defects or suggestions for improvements. They are usually unplanned. Author explains the product; colleague comes out with observations and author notes down relevant points and takes corrective actions.
   1. Inspection: Inspection is a thorough word-by-word checking of a software product with the intention of Locating defects, Confirming traceability of relevant requirements etc.
   How do test documents in a project span across the software development lifecycle?
   The following figure shows pictorially how test documents span across the software development lifecycle. The following discusses the specific testing documents in the lifecycle:
   
   • Central/Project test plan: This is the main test plan which outlines the complete test strategy of the software project. This document should be prepared before the start of the project and is used until the end of the software development lifecycle.
   • Acceptance test plan: This test plan is normally prepared with the end customer. This document commences during the requirement phase and is completed at final delivery.
   • System test plan: This test plan starts during the design phase and proceeds until the end of the project.
   • Integration and unit test plan: Both of these test plans start during the execution phase and continue until the final delivery.
   Which test cases are written first: white boxes or black boxes?
   Normally black box test cases are written first and white box test cases later. In order to write black box test cases we need the requirement document and, design or project plan. All these documents are easily available at the initial start of the project. White box test cases cannot be started in the initial phase of the project because they need more architecture clarity which is not available at the start of the project. So normally white box test cases are written after black box test cases are written.
   Black box test cases do not require system understanding but white box testing needs more structural understanding. And structural understanding is clearer i00n the later part of project, i.e., while executing or designing. For black box testing you need to only analyze from the functional perspective which is easily available from a simple requirement document.
   
   Explain Unit Testing, Integration Tests, System Testing and Acceptance Testing?
   Unit testing - Testing performed on a single, stand-alone module or unit of code.
   Integration Tests - Testing performed on groups of modules to ensure that data and control are passed properly between modules.
   System testing - Testing a predetermined combination of tests that, when executed successfully meets requirements.
   Acceptance testing - Testing to ensure that the system meets the needs of the organization and the end user or customer (i.e., validates that the right system was built).
   What is a test log?
   The IEEE Std. 829-1998 defines a test log as a chronological record of relevant details about the execution of test cases. It's a detailed view of activity and events given in chronological manner.
   The following figure shows a test log and is followed by a sample test log.
   
   Can you explain requirement traceability and its importance?
   In most organizations testing only starts after the execution/coding phase of the project. But if the organization wants to really benefit from testing, then testers should get involved right from the requirement phase.
   If the tester gets involved right from the requirement phase then requirement traceability is one of the important reports that can detail what kind of test coverage the test cases have.
   What does entry and exit criteria mean in a project?
   Entry and exit criteria are a must for the success of any project. If you do not know where to start and where to finish then your goals are not clear. By defining exit and entry criteria you define your boundaries.
   For instance, you can define entry criteria that the customer should provide the requirement document or acceptance plan. If this entry criteria is not met then you will not start the project. On the other end, you can also define exit criteria for your project. For instance, one of the common exit criteria in projects is that the customer has successfully executed the acceptance test plan.
   
   What is the difference between verification and validation?
   Verification is a review without actually executing the process while validation is checking the product with actual execution. For instance, code review and syntax check is verification while actually running the product and checking the results is validation.
   What is the difference between latent and masked defects?
   A latent defect is an existing defect that has not yet caused a failure because the sets of conditions were never met.
   A masked defect is an existing defect that hasn't yet caused a failure just because another defect has prevented that part of the code from being executed.
   Can you explain calibration?
   It includes tracing the accuracy of the devices used in the production, development and testing. Devices used must be maintained and calibrated to ensure that it is working in good order.
   What's the difference between alpha and beta testing?
   
   Alpha and beta testing has different meanings to different people. Alpha testing is the acceptance testing done at the development site. Some organizations have a different visualization of alpha testing. They consider alpha testing as testing which is conducted on early, unstable versions of software. On the contrary beta testing is acceptance testing conducted at the customer end.
   In short, the difference between beta testing and alpha testing is the location where the tests are done.
   How does testing affect risk?
   A risk is a condition that can result in a loss. Risk can only be controlled in different scenarios but not eliminated completely. A defect normally converts to a risk.
   
   What is coverage and what are the different types of coverage techniques?
   Coverage is a measurement used in software testing to describe the degree to which the source code is tested. There are three basic types of coverage techniques as shown in the following figure:
   
   • Statement coverage: This coverage ensures that each line of source code has been executed and tested.
   • Decision coverage: This coverage ensures that every decision (true/false) in the source code has been executed and tested.
   • Path coverage: In this coverage we ensure that every possible route through a given part of code is executed and tested.
   A defect which could have been removed during the initial stage is removed in a later stage. How does this affect cost?
   If a defect is known at the initial stage then it should be removed during that stage/phase itself rather than at some later stage. It's a recorded fact that if a defect is delayed for later phases it proves more costly. The following figure shows how a defect is costly as the phases move forward. A defect if identified and removed during the requirement and design phase is the most cost effective, while a defect removed during maintenance is 20 times costlier than during the requirement and design phases.
   
   For instance, if a defect is identified during requirement and design we only need to change the documentation, but if identified during the maintenance phase we not only need to fix the defect, but also change our test plans, do regression testing, and change all documentation. This is why a defect should be identified/removed in earlier phases and the testing department should be involved right from the requirement phase and not after the execution phase.
   What kind of input do we need from the end user to begin proper testing?
   The product has to be used by the user. He is the most important person as he has more interest than anyone else in the project.
   
   From the user we need the following data:
   • The first thing we need is the acceptance test plan from the end user. The acceptance test defines the entire test which the product has to pass so that it can go into production.
   • We also need the requirement document from the customer. In normal scenarios the customer never writes a formal document until he is really sure of his requirements. But at some point the customer should sign saying yes this is what he wants.
   • The customer should also define the risky sections of the project. For instance, in a normal accounting project if a voucher entry screen does not work that will stop the accounting functionality completely. But if reports are not derived the accounting department can use it for some time. The customer is the right person to say which section will affect him the most. With this feedback the testers can prepare a proper test plan for those areas and test it thoroughly.
   • The customer should also provide proper data for testing. Feeding proper data during testing is very important. In many scenarios testers key in wrong data and expect results which are of no interest to the customer.
   Can you explain the workbench concept?
   In order to understand testing methodology we need to understand the workbench concept. A Workbench is a way of documenting how a specific activity has to be performed. A workbench is referred to as phases, steps, and tasks as shown in the following figure.
   
   There are five tasks for every workbench:
   • Input: Every task needs some defined input and entrance criteria. So for every workbench we need defined inputs. Input forms the first steps of the workbench.
   • Execute: This is the main task of the workbench which will transform the input into the expected output.
   • Check: Check steps assure that the output after execution meets the desired result.
   • Production output: If the check is right the production output forms the exit criteria of the workbench.
   • Rework: During the check step if the output is not as desired then we need to again start from the execute step.
   
   
   Can you explain the concept of defect cascading?
   Defect cascading is a defect which is caused by another defect. One defect triggers the other defect. For instance, in the accounting application shown here there is a defect which leads to negative taxation. So the negative taxation defect affects the ledger which in turn affects four other modules.
   
   Can you explain cohabiting software?
   When we install the application at the end client it is very possible that on the same PC other applications also exist. It is also very possible that those applications share common DLLs, resources etc., with your application. There is a huge chance in such situations that your changes can affect the cohabiting software. So the best practice is after you install your application or after any changes, tell other application owners to run a test cycle on their application.
   
   What is the difference between pilot and beta testing?
   The difference between pilot and beta testing is that pilot testing is nothing but actually using the product (limited to some users) and in beta testing we do not input real data, but it's installed at the end customer to validate if the product can be used in production.
   
   What are the different strategies for rollout to end users?
   There are four major ways of rolling out any project:
   
   • Pilot: The actual production system is installed at a single or limited number of users. Pilot basically means that the product is actually rolled out to limited users for real work.
   • Gradual Implementation: In this implementation we ship the entire product to the limited users or all users at the customer end. Here, the developers get instant feedback from the recipients which allow them to make changes before the product is available. But the downside is that developers and testers maintain more than one version at one time.
   • Phased Implementation: In this implementation the product is rolled out to all users in incrementally. That means each successive rollout has some added functionality. So as new functionality comes in, new installations occur and the customer tests them progressively. The benefit of this kind of rollout is that customers can start using the functionality and provide valuable feedback progressively. The only issue here is that with each rollout and added functionality the integration becomes more complicated.
   • Parallel Implementation: In these types of rollouts the existing application is run side by side with the new application. If there are any issues with the new application we again move back to the old application. One of the biggest problems with parallel implementation is we need extra hardware, software, and resources.
   What's the difference between System testing and Acceptance testing?
   Acceptance testing checks the system against the "Requirements." It is similar to System testing in that the whole system is checked but the important difference is the change in focus:
   System testing checks that the system that was specified has been delivered. Acceptance testing checks that the system will deliver what was requested. The customer should always do Acceptance testing and not the developer.
   The customer knows what is required from the system to achieve value in the business and is the only person qualified to make that judgement. This testing is more about ensuring that the software is delivered as defined by the customer. It's like getting a green light from the customer that the software meets expectations and is ready to be used.
   Can you explain regression testing and confirmation testing?
   Regression testing is used for regression defects. Regression defects are defects occur when the functionality which was once working normally has stopped working. This is probably because of changes made in the program or the environment. To uncover such kind of defect regression testing is conducted.
   The following figure shows the difference between regression and confirmation testing.
   
   If we fix a defect in an existing application we use confirmation testing to test if the defect is removed. It's very possible because of this defect or changes to the application that other sections of the application are affected. So to ensure that no other section is affected we can use regression testing to confirm this.

'Petya' ransomware attack: what is it and how can it be stopped?

Many organizations in Europe and the US have been crippled by a ransomware attack known as “Petya”. The malicious software has spread through large firms including the advertiser WPP, food company Mondelez, legal firm DLA Piper and Danish shipping and transport firm Maersk, leading to PCs and data being locked up and held for ransom.

It’s the second major global ransomware attack in the past . In early May, Britain’s National Health Service (NHS) was among the organizations infected by WannaCry, which used a vulnerability first revealed to the public as part of a leaked stash of NSA-related documents released online in April by a hacker group calling itself the Shadow Brokers.

Ransomware attack 'not designed to make money', researchers claim

The WannaCry or WannaCrypt ransomware attack affected more than 230,000 computers in over 150 countries, with the NHS, Spanish phone company Telefónica and German state railways among those hardest hit.

Like WannaCry, “Petya” spreads rapidly through networks that use Microsoft Windows, but what is it, why is it happening and how can it be stopped?

What is ransomware?

Ransomware is a type of malware that blocks access to a computer or its data and demands money to release it.

How does it work?

When a computer is infected, the ransomware encrypts important documents and files and then demands a ransom, typically in Bitcoin, for a digital key needed to unlock the files. If victims don’t have a recent back-up of the files they must either pay the ransom or face losing all of their files.

How does the “Petya” ransomware work?

The ransomware takes over computers and demands $300, paid in Bitcoin. The malicious software spreads rapidly across an organization once a computer is infected using the EternalBlue vulnerability in Microsoft Windows (Microsoft has released a patch, but not everyone will have installed it) or through two Windows administrative tools. The malware tries one option and if it doesn’t work, it tries the next one. “It has a better mechanism for spreading itself than WannaCry,” said Ryan Kalember, of cybersecurity company Proofpoint.

Is there any protection?

Advertisement

Most major antivirus companies now claim that their software has updated to actively detect and protect against “Petya” infections: Symantec products using definitions version 20170627.009 should, for instance, and Kaspersky also says its security software is now capable of spotting the malware. Additionally, keeping Windows up to date – at the very least through installing March’s critical patch defending against the EternalBlue vulnerability – stops one major avenue of infection, and will also protect against future attacks with different payloads.
For this particular malware outbreak, another line of defence has been discovered: “Petya” checks for a read-only file, C:\Windows\perfc.dat, and if it finds it, it won’t run the encryption side of the software. But this “vaccine” doesn’t actually prevent infection, and the malware will still use its foothold on your PC to try to spread to others on the same https://www.facebook.com/ravi.tyagi.55https://www.facebook.com/ravi.tyagi.55.

Why is it called “Petya”?

Strictly speaking, it is not. The malware appears to share a significant amount of code with an older piece of ransomware that really was called Petya, but in the hours after the outbreak started, security researchers noticed that “the superficial resemblance is only skin deep”. Researchers at Russia’s Kaspersky Lab redubbed the malware NotPetya, and increasingly tongue-in-cheek variants of that name – Petna, Pneytna, and so on – began to spread as a result. On top of that, other researchers who independently spotted the malware gave it other names: Romanian’s Bitdefender called it Goldeneye, for instance.

Hackers publish private photos from cosmetic surgery clinic

Where did it start? 

The attack appears to have been seeded through a software update mechanism built into an accounting program that companies working with the Ukrainian government need to use, according to the Ukrainian cyber police. This explains why so many Ukrainian organizations were affected, including government, banks, state power utilities and Kiev’s airport and metro system. The radiation monitoring system at Chernobyl was also taken offline, forcing employees to use hand-held counters to measure levels at the former nuclear plant’s exclusion zone. A second wave of infections was spawned by a phishing campaign featuring malware-laden attachments.

How far has it spread?

The “Petya” ransomware has caused serious disruption at large firms in Europe and the US, including the advertising firm WPP, French construction materials company Saint-Gobain and Russian steel and oil firms Evraz and Rosneft. The food company Mondelez, legal firm DLA Piper, Danish shipping and transport firm AP Moller-Maersk and Heritage Valley Health System, which runs hospitals and care facilities in Pittsburgh, also said their systems had been hit by the malware.
Crucially, unlike WannaCry, this version of ‘Petya’ tries to spread internally within networks, but not seed itself externally. That may have limited the ultimate spread of the malware, which seems to have seen a decrease in the rate of new infections overnight.

UK energy industry cyber-attack fears are 'off the scale'

Who is behind the attack?

It is not clear, but it seems likely it is someone who wants the malware to masquerade as ransomware, while actually just being destructive, particularly to the Ukrainian government. Security researcher Nicholas Weaver told cybersecurity blog Krebs on Security that ‘Petya’ was a “deliberate, malicious, destructive attack or perhaps a test disguised as ransomware”. Pseudonymous security researcher Grugq noted that the real Petya “was a criminal enterprise for making money,” but that the new version “is definitely not designed to make money.

Advertisement

“This is designed to spread fast and cause damage, with a plausibly deniable cover of ‘ransomware,’” he added, pointing out that, among other tells, the payment mechanism in the malware was inept to the point of uselessness: a single hardcoded payment address, meaning the money can be traced; the requirement to email proof of payment to a webmail provider, meaning that the email address can be – and was – disabled; and the requirement to send an infected machine’s 60-character, case sensitive “personal identification key” from a computer which can’t even copy-and-paste, all combine to mean that “this payment pipeline was possibly the worst of all options (sort of ‘send a personal cheque to: Petya Payments, PO Box … ’)”.
Ukraine has blamed Russia for previous cyber-attacks, including one on its power grid at the end of 2015 that left part of western Ukraine temporarily without electricity. Russia has denied carrying out cyber-attacks on Ukraine.

What should you do if you are affected by the ransomware?

The ransomware infects computers and then waits for about an hour before rebooting the machine. While the machine is rebooting, you can switch the computer off to prevent the files from being encrypted and try and rescue the files from the machine, as flagged by @HackerFantastic on Twitter.

If the system reboots with the ransom note, don’t pay the ransom – the “customer service” email address has been shut down so there’s no way to get the decryption key to unlock your files anyway. Disconnect your PC from the internet, reformat the hard drive and reinstall your files from a backup. Back up your files regularly and keep your anti-virus software up to date.

Since you’re here …

… we have a small favour to ask. More people are reading the Guardian than ever but advertising revenues across the media are falling fast. And unlike many news organisations, we haven’t put up a paywall – we want to keep our journalism as open as we can. So you can see why we need to ask for your help. The Guardian’s independent, investigative journalism takes a lot of time, money and hard work to produce. But we do it because we believe our perspective matters – because it might well be your perspective, too.

I appreciate there not being a paywall: it is more democratic for the media to be available for all and not a commodity to be purchased by a few. I’m happy to make a contribution so others with less means still have access to information. Thomasine F-R.

If everyone who reads our reporting, who likes it, helps to support it, our future would be much more secure. 

10k - dal yn fyw!

Neithiwr, fe wyliais raglen Cwmni Da - Merêd - sef portread o Dr Meredydd Evans. Anhygoel meddwl bydd o'n 95 eleni. Ac anhygoel meddwl am yr hyn mae o wedi gyflawni yn ei fywyd.

Roedd hi'n raglen gynnil a syml, ac roedd hyn yn ein galluogi fel gwylwyr i ganolbwyntio ar Merêd a'r hyn 'roedd yn ei ddweud. Roedd hi'n raglen emosiynol iawn hefyd, ac amryw o weithiau, fe lanwodd fy llygaid a dagrau wrth iddo rannu gyda ni ei feddyliau am Gymru, y Gymraeg a'i fywyd. Ac wrth gwrs, ei berthynas a Phyllis. Cefais y fraint o dreulio cryn amser yng nghwmni Phyllis pam wnaeth fy rhieni raglen deledu amdani. Roedd yn amser arbennig iawn, ac fe greodd gryn argraff arna'i. Ac fe gawsom goblyn o hwyl hefyd.

Ond yn ol at neithiwr. Mae nifer o'r hyn ddywedodd Merêd wedi pigo fy nghydwybod. Heb os, mae o wedi dangos dewrder a chryfder drwy ei fywyd wrth ymladd dros barhad yr iaith. Er mod i'n ei adnabod, ac yn ymwybodol o nifer o bethau mae wedi ei gyflawni, doeddwn i ddim yn ymwybodol neu'n cofio mai mewn araith yn yr Eisteddfod Genedlaethol y rhybuddiodd yn gadarn ynglyn a dyfodol yr iaith. Ac er gwaetha'r ffaith fod pobl wedi ei gyhuddo o fod yn hiliol oherwydd ei sylwadau, fo oedd yn llygad ei le. Gresyn na wnaeth mwy o bobl gymryd sylw amser hynny, a gweithredu. Mi yda ni, yn anffodus, yn rhy barod i fod yn obeithiol yn hytrach na wynebu'r hyn sydd yn digwydd o'n cwmpas, mewn cymunedau ledled Cymru. Er ein bod yn cytuno. ar y cyfan, fod rhaid gwneud rhywbeth am y peth a'i bod yn sefyllfa drist, lle mae'r gweithredu fydd yn gwneud gwahaniaeth gwirioneddol? A beth sydd wedi digwydd mewn gwirionedd i atal dirywiad pellach o ran nifer siaradwyr Cymraeg ers cyhoeddi canlyniadau'r Cyfrifiad diwethaf? Yda ni rhy 'boleit' fel Cymry Cymraeg i wneud yr hyn sydd ei angen?

Nid son ydw i ynglyn a phroestio ac ati. Ond yn hytrach gweithredu o ran newid polisiau ar lefel leol a chenedlaethol fydd yn creu newid gwirioneddol. Pam na fu fwy o drafod ar syniadau radical, newydd, megis rhai Adam Price yn ei bapur Arfor a ganfyddir drwy glicio yma.Tydw i ddim yn honni bod cynllun Adam yn berffaith, ond mae'r syniadau sydd yn y papur hwn werth eu trafod a'u datblygu ymhellach. Mae nhw'n gyffrous. Mae nhw'n cynnig gobaith gwirioneddol i barhad y Gymraeg. Pam na wnawn ni ystyried gwneud rhywbeth hollol wahanol, cyn i bethau waethygu?

A dyma pam mae fy nghydwybod yn teimlo'n anestmwyth. Beth ydw i wedi ei wneud, mewn gwirionedd, i ymateb i heriadau o'r fath? Ambell araith. Ambell erthygl. Cwyno gyda ffrindiau. Helpu i gyhoeddi papur Adam. Ond wedi hynny, dim. A dwi'n teimlo cywilydd mawr am hynny. Fedra'i ddim bodloni ar gwyno a disgwyl i eraill ddatrys y broblem os ydi pobl 94 oed yn gwneud gymaint mwy!

Dwi'm isho cyrraedd diwedd fy oes, a meddwl mod i heb drio fy ngorau i frwydro dros ddyfodol gwlad a iaith dwi'n credu'n angerddol ynddi. A diolch i raglen neithiwr, a geiriau Merêd am fy atgoffa o hynny. A gan fy mod mewn hwyliau sentimental, dwi am eich gadael am heno hefo un o fy hoff gerddi gan T.H.Parry Williams, sy'n dod i'r cof yn aml pan dwi'n meddwl am fod yn Gymraes!

Hon 

Beth yw’r ots gennyf i am Gymru? Damwain a hap
Yw fy mod yn ei libart yn byw. Nid yw hon ar fap

Yn ddim byd ond cilcyn o ddaear mewn cilfach gefn,
Ac yn dipyn o boendod i’r rhai sy’n credu mewn trefn.

A phwy sy’n trigo’n y fangre, dwedwch i mi.
Dim ond gwehilion o boblach? Peidiwch, da chwi

 chlegar am uned a chenedl a gwlad o hyd;
Mae digon o’r rhain, heb Gymru, i’w cael yn y byd.

Rwyf wedi alaru ers talm ar glywed grwn
Y Cymry bondigrybwyll, yn cadw swn.

Mi af am dro, i osgoi eu lleferydd a’i llên,
Yn ôl i’m cynefin gynt, a’m dychymyg yn drên.

A dyma fi yno. Diolch am fod ar goll
Ymhell o gyffro geiriau’r eithafwyr oll.

Dyma’r Wyddfa a’i chriw; dyma lymder a moelni’r tir;
Dyma’r llyn a’r afon a’r clogwyn; ac, ar fy ngwir,

Dacw’r ty lle’m ganed. Ond wele, rhwng llawr a ne’
Mae lleisiau a drychiolaeth ar hyd y lle.

Rwy’n dechrau simsanu braidd; ac meddaf i chwi,
Mae rhyw ysictod fel petai’n dod drosof i;

Ac mi glywaf grafangau Cymru’n dirdynnu fy mron.
Duw a’m gwaredo, ni allaf ddianc rhag hon.

SUNDAY, NOVEMBER 17, 2013

10k - dal yn fyw!

Mae gen i ychydig o gywilydd mod i wedi bod yn poeni cryn gymaint am gwbwlhau fy ras 10k gyntaf erioed. Yn arbennig felly o weld ar Twitter a Facebook pa mor aml mae nifer o fy ffrindiau yn rhedeg hyn neu'n bellach jest am hwyl, heb son am faint sy'n cwbwlhau marathon o leiaf dwy waith y flwyddyn. Ond - mae'n rhaid i bawb ddechrau'n rhywle yn does. A dyma oedd fy nechrau i heddiw 'ma, fel rhan o Morunning ym mharc Bute Caerdydd.

Roeddwn yn rhedeg fel rhan o dim Fit Mums South Wales, sydd yn grwp ymarfer corff rwyf yn mynychu. Syniad ein hyfforddwraig, Abi, oedd annog 35 ohonom i redeg a dwi'n falch iddi wneud hynny. Ffordd dda o sicrhau ein bod yn ymarfer corff yn rheolaidd ers i'r clociau droi nol, a profi gallwn fod yn fwy ffit nag oeddem cyn cael plant! Roedd yna awyrgylch arbennig wrth imi redeg, ynghyd a chefnogaeth aruthrol drwy gydol yr amser roeddwn yn rhedeg er fy mod yn araf fel malwen. Y peth pwysicaf i bawb oedd cefnogi'r elusen - a cwbwlhau! (Fe enillodd Abi y 10k gyda llaw!)

Dwi'n berson hynod o gystadleuol fel arfer, ond roedd rhaid imi dderbyn heddiw nad oeddwn ym mynd i gwbwlhau mewn amser cyflym. Yn wir, dwi'n siwr bod rhai pobl yn cerdded 10k yn gynt na dwi'n medru ei redeg. Ond dyna ni. I ddynes oedd methu rhedeg o gwbwl drwy gydol fy mywyd, dwi'n hapus mod i wedi llwyddo i orffen. A dim ond gwella medrith fy amser erbyn flwyddyn 'nesa!

Diolch i Geraint a Twm am ddod i fy nghefnogi. A diolch i bawb am y geiriau o gefnogaeth, unai wyneb yn wyneb neu drwy rydweithiau cymdeithasol. Bu'n hwb aruthrol. Hynny, a gwrando ar gerddoriaeth Bryn Fon a Tom Jones ar fy ipod wrth redeg o gwmpas! Diolch iddynt hwythau hefyd am fy nghadw i fynd!

TUESDAY, SEPTEMBER 24, 2013

Ein Priodas - Our Wedding

Ar y 7fed o Fedi, fe briododd Geraint Day a minnau yn Gregynog, Sir Drefaldwyn. Roedd yn ddiwrnod bythgofiadwy, a gan mod i'n arfer rhannu digwyddiadau fy mywyd yma, dyma lun neu ddau o'r diwrnod wedi eu tynnu gan Keith Morris. Teimlo'n ddynes lwcus iawn.

On the 7th September, Geraint Day and I were married at Gregynog Hall, Montgomeryshire. It was a fantastic day, and as I usually share my live events on my blog, here are a few photos taken by Keith Morris. I feel like the luckiest woman on earth!

THURSDAY, SEPTEMBER 19, 2013

Môn a San Steffan

Yn groes i’r hyn sydd wedi cael ei ysgrifennu gan ambell berson, does dim sail i’r si fy mod wedi rhoi fy enw gerbron fel ymgeisydd Plaid Cymru ar gyfer sedd Ynys Môn yn San Steffan. A hoffwn gadarnhau yma na fyddaf yn gwneud chwaith.

Doedd o ddim yn benderfyniad hawdd. Ers imi gystadlu am sedd y Cynulliad ym Mehefin, mae nifer o aelodau Môn wedi cysylltu â mi yn gofyn imi roi fy enw gerbron ac yn datgan eu cefnogaeth. Heb os, cefais fy nhemtio. Dyma’r ardal lle cefais fy magu. Dwi’n teimlo’n agerddol dros yr Ynys, ac yn poeni am ei dyfodol. A dwi’n parchu aelodau’r Blaid ym Môn hefyd ac yn casáu meddwl mod i’n siomi nifer ohonynt drwy beidio mynd am yr enwebiad. Dwi’n grediniol bod gan y Blaid obaith gwirioneddol o gipio’r sedd oddi ar y Blaid Lafur yn 2015 yn sgil canlyniadau gwych eleni yn etholiadau’r Cyngor Sir a wedyn buddugoliaeth ysgubol Rhun. Dwi’n siŵr y bydd hi’n ymgyrch egnïol a difyr. Pe byddwn wedi sefyll a chael fy mabwysiadu yn ymgeisydd, fe fyddwn wedi symud i Fôn ac ymgyrchu yn galed i adennill y sedd a mwynhau pob eiliad. Ond, er gwaetha’r temtasiwn o gael cyfle posibl i fod yn Aelod Seneddol benywaidd cyntaf Plaid Cymru a sicrhau bod Môn yn wyrdd yn San Steffan hefyd, mae yna resymau pam fy mod wedi penderfynu peidio mynd amdani. Ac i roi taw ar y sibrydion, mae’n well imi fod yn agored am y peth, a rhannu fy rhesymau hefo chi.

Y prif reswm ydi hyn: Aelod Cynulliad nid Aelod Seneddol fyddwn i’n hoffi bod. Dwi wedi gweithio yn San Steffan i Aelodau Seneddol y Blaid. Dwi’n deall y swydd, a pha mor galed maen nhw’n gweithio yno. Mae’r oriau yn faith. Ac mae’r bywyd yn Llundain yn un hynod o unig. Fedrwch chi ddim dod a’ch teulu hefo chi, a fasa nhw ddim yn eich gweld chi beth bynnag oherwydd oriau’r Senedd. I berson sengl neu rywun hŷn, mae hyn yn iawn. Ond - pedwar mis oed ydi Twm, fy mab. Byddai bod yn Aelod Seneddol yn golygu peidio ei weld am dair neu bedair noson bob wythnos yn ystod tymor y Senedd. Mi fasa’n torri fy nghalon i wneud hynny. Fasa'r un peth ddim yn wir am y Cynulliad wrth gwrs. Er bod Caerdydd yn bell iawn o’r Gogledd, y gwir amdani ydi y byddai’n bosib i Twm drafeilio hefo fi i Gaerdydd. Mae oriau gwaith y Cynulliad yn llawer mwy cyfeillgar i deuluoedd, a gallwn ei weld mwy neu lai bob nos. Hyd yn oed ar ôl iddo ddechrau yn yr ysgol, gallwn wneud fel mae ambell Aelod Cynulliad arall wedi ei wneud, a’i yrru i ysgol yng Nghaerdydd. Byddai yno hefo fi drwy’r wythnos, ac i fyny yn y Gogledd ar y penwythnosau. Er nad yw hynny’n ddelfrydol, byddai’n golygu na fyddwn i’n gorfod dewis rhwng gyrfa wleidyddol neu fod yn Fam. 

Cofiwch chi, nid pawb sy’n cytuno y dylwn i geisio cael fy ethol i’r Cynulliad rŵan mod i’n Fam. Cefais sioc fawr, a fy siomi, o dderbyn tua hanner dwsin o negeseuon digon ffiaidd ar ol mynd am enwebiad Môn pan oedd  Twm yn chwe wythnos oed. A dwn i ddim faint o bobl ddywedodd wrthai yn yr Eisteddfod ei bod yn fendith na chefais fy newis er mwyn imi allu bod yn “Fam Iawn” i Twm. Dywedwyd bod gennyf ddigon o amser i fynd am y Cynulliad pan mae o’n hŷn. Tan hynny, ro’n i wastad wedi meddwl bod ein cymdeithas wedi newid a bod dynion a merched bellach yn gyfartal. Ond crafwch dan yr wyneb, ac edrych ar rai o’r sylwadau sy’n ymddangos ar Golwg 360, ac mi welwch chi pa mor barod ydi pobl i feirniadu merched sydd yn meiddio herio, a dangos unrhyw fath o uchelgais. Bitsh neu ast ydach chi os dangoswch unrhyw fath o dân, tra bod dynion cyffelyb yn “gryf”, ac yn “arweinwyr cenedl”. Bonws ydi’r ffaith bod nhw’n ddynion teulu. Does neb yn gweld bai arnyn nhw am adael eu plant er mwyn dilyn eu huchelgais wleidyddol. Dim rhyfedd bod llai o ferched  yn fodlon rhoi eu henwau ymlaen pan mai dyma’r math o agweddau sydd yn ein hwynebu. 

Ond, er imi gael fy nadrithio rywfaint gan rai o’r agweddau hyn, dwi ddim am adael i ambell unigolyn sexist ennill chwaith. Mae’r mwyafrif o bobl wedi bod yn gefnogol imi, a dwi am barhau i geisio cael fy ethol yn Aelod Cynulliad. Caerdydd ydi’r lle i fod, nid Llundain. Yn wir, dwi’n mawr obeithio na fydda ni angen gyrru neb i Lundain cyn hir ac y bydd grym ein Senedd ein hunain yn parhau i gynyddu. Mae bod yn brif blaid yn y Cynulliad o fewn ein cyrraedd, a hoffwn fod yn rhan o’r tîm sy’n arwain ein cenedl tuag at annibyniaeth.

Dwi’n poeni am ddyfodol Cymru, a hoffwn gael y cyfle i chwarae rhan flaenllaw mewn newid ein cenedl er gwell. Dwi isho arwain drwy esiampl, yn hytrach na chwyno o’r ochrau. Dwi’n poeni hefyd am ddyfodol yr ardaloedd lle y cefais fy magu ym Mon ac Arfon, ac am y bobl sydd yn ei chael hi’n anodd cynnal bywoliaeth yno neu ganfod swydd. Dwi’n gwybod o brofiad pa mor brin ydi swyddi yno. Dwi’n un o’r bobl sydd wedi gorfod symud i Gaerdydd i ganfod swydd gan nad oedd un addas ar gael yn y Gogledd. Gall Aelod Cynulliad wneud cymaint o wahaniaeth ar ran ei etholwyr, a dyna brif apêl y swydd i mi. Hyd nes daw’r cyfle i sefyll, byddaf yn parhau yn aelod gweithgar ar draws Cymru, ac yn cefnogi ein hymgeiswyr ym mhob etholiad. Er mai ym Mhontypridd dwi’n byw ar y funud, mae fy nghalon yn parhau yn y Gogledd ac yno dwi’n gweld fy nyfodol.

Dwi’n edrych ymlaen at weld pwy fydd yn sefyll ym Môn ar gyfer San Steffan, a pwy gaiff eu dewis. Pob lwc i bawb sydd yn ddigon dewr i fynd amdani. Dwi’n edrych ymlaen at gefnogi ymgyrch y person buddugol a’u helpu, gobeithio, i ennill y sedd. Dyna fyddai’r canlyniad gorau posibl, nid i Blaid Cymru yn unig, ond i bobl Môn hefyd.

SUNDAY, JUNE 30, 2013

Rollercoaster

Well, the past week and a half has been something of a rollercoaster. One minute I was going for Arfon, the next minute I was being urged to pull out of the race and go for Ynys Mon as Ieuan had stepped down of the Assembly with immediate effect and a by-election was imminent. As an Anglesey girl, it had always been my dream to represent the island and though the timing wasn't ideal (given that my son was only six weeks old), I decided to go for it.

Whilst some were advising me to keep my name in for both constituencies, I felt that wouldn't be fair on either Arfon or Ynys Mon. Ideally, both selections wouldn't have taken place during the same week but c'est la vie. Yes, standing down from one race to enter another did open me up to criticism that I was a political butterfly but believe me, it was one of the toughest decisions I've ever made. I had a lot of support in Arfon, and I hated letting people down by pulling out of the race. But on the other hand, I had people I've known all my life asking me to go for Ynys Mon...

Do I regret that decision? No. And if placed in the same position again, I would make the same decision. But I do regret how things came about, and that Ynys Mon had to rush the selection process. I did, however, enjoy the hustings. I was impressed by Ann, and though we were facebook friends prior to this week, I feel we definitely became real friends through the experience. I was also glad to have the opportunity to debate Wylfa, and explain my opposition to nuclear power in a constructive way.

I wish Rhun all the best. He has a fantastic team of people to help him in Anglesey, and I know they'll support him 100%. They know what they're doing, as was proven during the recent council elections on the island, and Plaid Cymru should have no problem keeping the seat. I look forward to going out to campaign during the next month, and taking Plaid's positive message out to the people of Ynys Mon.

FRIDAY, JUNE 21, 2013

Mynd am Fôn

Maen nhw’n dweud bod wythnos yn amser hir mewn gwleidyddiaeth. Mae hynny’n sicr yn wir am wythnos yma. Pan roddais fy enw i mewn yn Arfon i gael fy ystyried fel ymgeisydd Plaid Cymru yn etholiad y Cynulliad yn 2016, doedd dim awgrym na fyddai Ieuan Wyn Jones yn sefyll ym Môn eto. Fel yr ydym bellach yn gwybod, mae’r sefyllfa wedi newid yn syfrdanol o sydyn ac mae is-etholiad ar y gorwel yn fuan yn dilyn ei ymadawiad disymwth ddoe.

Ar ôl dwys ystyried, ac ar ôl derbyn nifer o negeseuon o gefnogaeth gan aelodau Ynys Môn, teimlaf fod yn rhaid imi ddilyn fy nghalon. Rwyf wedi penderfynu tynnu fy enw o’r ras am Arfon ac ymroddi’n llwyr i geisio cael fy newis i sefyll ar ran y Blaid yn is-etholiad Ynys Môn.

Mae’n ddrwg gen i siomi’r nifer o bobl yn Arfon oedd wedi datgan eu cefnogaeth imi, ond rwyf yn siwr y byddant yn deall fy nghyfyng gyngor a fy mhenderfyniad.

Hoffwn ddymuno pob lwc i’r ymgeisydd sydd ar ôl yn y ras, Sian Gwenllian.

Going for Môn

They say a week is a long time in politics. That’s certainly true of events this week. When I put my name forward to be considered as the next Plaid Cymru candidate for the 2016 Assembly election in Arfon, there was no indication that Ieuan Wyn Jones might not be standing in Anglesey again. As we now know, that situation has changed rapidly and a by-election is imminent after his departure yesterday.

Following careful consideration and many messages of encouragement from members in Ynys Mon, I feel I have to follow my heart. I have decided to withdraw from the race for Arfon to give my all in my bid to be selected as Plaid Cymru’s candidate in the Ynys Mon by-election.

To the many people of Arfon who had pledged their support for me, I am sorry to disappoint them but I’m sure they’ll understand my dilemma and my decision.

I would like to wish the remaining candidate, Sian Gwenllian, every success.