Yinkay007's Posts
Nairaland Forum › Yinkay007's Profile › Yinkay007's Posts
1 2 3 4 5 6 7 8 9 10 (of 11 pages)
Here are some Software Testers Interview Questions 1What is the role of QA in development project? Deploy and enforce standards Continually improve standards, QA process based on previous experiences, Promote effective means for reporting and communication. 2What is verification? A: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, and walkthroughs and inspection meetings. 3What is validation? A: Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed. What is quality? A: Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable Continue reading on https://sharptester.com/2017/10/20/software-testers-interview1/ |
Many Companies underestimate the importance of static testing during product development. let me start by stating what is stating testing and how it is different from dynamic testing. Static testing. can be defined as software testing technique that involves examination of the program's code/requirement/design and its associated documentation/artifacts without the program be executed Dynamic testing on the other hand involves the actual execution of the software of a component or system. During static testing the major objective is to prevent defect from being implemented into the system and also to educate other team members. Static testing is done before Dynamic testing. Errors/defects identified during static testing are less costly as they could be fixed before being implemented. There are two main terms used during static testing which are static analysis and review. Although static analysis is performed by developers and supporting by different tools. Continue Reading on https://sharptester.com/2017/10/16/static-testing-neccessary/ |
Many Companies underestimate the importance of static testing during product development. let me start by stating what is stating testing and how it is different from dynamic testing. Static testing. can be defined as software testing technique that involves examination of the program's code/requirement/design and its associated documentation/artifacts without the program be executed Dynamic testing on the other hand involves the actual execution of the software of a component or system. During static testing the major objective is to prevent defect from being implemented into the system and also to educate other team members. Static testing is done before Dynamic testing. Errors/defects identified during static testing are less costly as they could be fixed before being implemented. There are two main terms used during static testing which are static analysis and review. Although static analysis is performed by developers and supporting by different tools. Continue Reading on https://sharptester.com/2017/10/16/static-testing-neccessary/ |
Many Companies underestimate the importance of static testing during product development. let me start by stating what is stating testing and how it is different from dynamic testing. Static testing. can be defined as software testing technique that involves examination of the program's code/requirement/design and its associated documentation/artifacts without the program be executed Dynamic testing on the other hand involves the actual execution of the software of a component or system. During static testing the major objective is to prevent defect from being implemented into the system and also to educate other team members. Static testing is done before Dynamic testing. Errors/defects identified during static testing are less costly as they could be fixed before being implemented. There are two main terms used during static testing which are static analysis and review. Although static analysis is performed by developers and supporting by different tools. Continue Reading on https://sharptester.com/2017/10/16/static-testing-neccessary/ |
yinkay007: |
yinkay007: |
yinkay007: |
nigeriannwa:Maybe your browser doesnt support the website. Try another |
Below are some Excuses Every Software Tester Must Stop Giving 1. We don’t deploy our builds, other team are responsible for doing that for us:This is one of the excuse we have experienced from testers over the years. Considering scenarios like entering into the office one day and as a tester you notice that there are few issues with the product build causing a show-stopper(blocker). In this case a new build is needed urgently to be built from the repository. You raise a request or contact the Development team for this request 2. We don’t control our Test Environment, we have (read ‘very’) limited access: I do hear this excuse a lot from testers- we have only read only access to the test environment and some even say they have only access to logs. The development team have the full access to the environment and not us 3. We as Testers don’t debug an issue, we find defects and log it- Testers have the habit of logging defects and not assiting or getting to understand the root cause and how it was resolved. Continue reading on Sharptester.com and also check how to mitigate against all these by clicking the lik below for the http://sharptester.com/2017/10/03/various-excuses-every-software-tester-must-stop-giving/ |
Below are some Excuses Every Software Tester Must Stop Giving 1. We don’t deploy our builds, other team are responsible for doing that for us:This is one of the excuse we have experienced from testers over the years. Considering scenarios like entering into the office one day and as a tester you notice that there are few issues with the product build causing a show-stopper(blocker). In this case a new build is needed urgently to be built from the repository. You raise a request or contact the Development team for this request 2. We don’t control our Test Environment, we have (read ‘very’) limited access: I do hear this excuse a lot from testers- we have only read only access to the test environment and some even say they have only access to logs. The development team have the full access to the environment and not us 3. We as Testers don’t debug an issue, we find defects and log it- Testers have the habit of logging defects and not assiting or getting to understand the root cause and how it was resolved. Continue reading on Sharptester.com and also check how to mitigate against all these by clicking the lik below for the http://sharptester.com/2017/10/03/various-excuses-every-software-tester-must-stop-giving/ |
Below are some Excuses Every Software Tester Must Stop Giving 1. We don’t deploy our builds, other team are responsible for doing that for us:This is one of the excuse we have experienced from testers over the years. Considering scenarios like entering into the office one day and as a tester you notice that there are few issues with the product build causing a show-stopper(blocker). In this case a new build is needed urgently to be built from the repository. You raise a request or contact the Development team for this request 2. We don’t control our Test Environment, we have (read ‘very’) limited access: I do hear this excuse a lot from testers- we have only read only access to the test environment and some even say they have only access to logs. The development team have the full access to the environment and not us 3. We as Testers don’t debug an issue, we find defects and log it- Testers have the habit of logging defects and not assiting or getting to understand the root cause and how it was resolved. Continue reading on Sharptester.com and also check how to mitigate against all these by clicking the lik below for the http://sharptester.com/2017/10/03/various-excuses-every-software-tester-must-stop-giving/ |
Below are some Excuses Every Software Tester Must Stop Giving 1. We don’t deploy our builds, other team are responsible for doing that for us:This is one of the excuse we have experienced from testers over the years. Considering scenarios like entering into the office one day and as a tester you notice that there are few issues with the product build causing a show-stopper(blocker). In this case a new build is needed urgently to be built from the repository. You raise a request or contact the Development team for this request 2. We don’t control our Test Environment, we have (read ‘very’) limited access: I do hear this excuse a lot from testers- we have only read only access to the test environment and some even say they have only access to logs. The development team have the full access to the environment and not us 3. We as Testers don’t debug an issue, we find defects and log it- Testers have the habit of logging defects and not assiting or getting to understand the root cause and how it was resolved. Continue reading on Sharptester.com and also check how to mitigate against all these by clicking the lik below for the http://sharptester.com/2017/10/03/various-excuses-every-software-tester-must-stop-giving/ |
Below are some Excuses Every Software Tester Must Stop Giving 1. We don’t deploy our builds, other team are responsible for doing that for us:This is one of the excuse we have experienced from testers over the years. Considering scenarios like entering into the office one day and as a tester you notice that there are few issues with the product build causing a show-stopper(blocker). In this case a new build is needed urgently to be built from the repository. You raise a request or contact the Development team for this request 2. We don’t control our Test Environment, we have (read ‘very’) limited access: I do hear this excuse a lot from testers- we have only read only access to the test environment and some even say they have only access to logs. The development team have the full access to the environment and not us 3. We as Testers don’t debug an issue, we find defects and log it- Testers have the habit of logging defects and not assiting or getting to understand the root cause and how it was resolved. Continue reading on Sharptester.com and also check how to mitigate against all these by clicking the lik below for the http://sharptester.com/2017/10/03/various-excuses-every-software-tester-must-stop-giving/ |
[quote author=yinkay007 post=60608902][/quote] |
yinkay007: |
yinkay007: |
yinkay007: |
yinkay007: |
[quote author=yinkay007 post=60054335][/quote] |
[quote author=yinkay007 post=60215433][/quote] |
Sharptester.com offers test tools trainings on the best and most widely used tools across the world. We offer practical and online trainings on the following test tools for Test management , Automation, performance and defect management Testrail JIRA Bugzilla Selenium QTP LoadRunner LoadUI SoapUI e.t.c. To Read more on the Tools and Learn kindly visit http://sharptester.com/2017/09/19/software-testing-tools-training/ We are proud to offer these services to Nigerians. |
yinkay007: |
yinkay007: |
yinkay007: |
API testing is a test that is performed to confirm that API's executes successfully, return the correct value when executed based on the input conditions, update any data structure as expected and also triggers some other event or calls another API. read more to view What You Need to start API testing and also API Testing tools through the link below http://sharptester.com/2017/09/18/api-testing-api-test-tools/ |
API testing is a test that is performed to confirm that API's executes successfully, return the correct value when executed based on the input conditions, update any data structure as expected and also triggers some other event or calls another API. read more to view What You Need to start API testing and also API Testing tools through the link below http://sharptester.com/2017/09/18/api-testing-api-test-tools/ (Modify) (Quote) (Report) (Share) |
API testing is a test that is performed to confirm that API's executes successfully, return the correct value when executed based on the input conditions, update any data structure as expected and also triggers some other event or calls another API. read more to view What You Need to start API testing and also API Testing tools through the link below http://sharptester.com/2017/09/18/api-testing-api-test-tools/ |
API testing is a test that is performed to confirm that API's executes successfully, return the correct value when executed based on the input conditions, update any data structure as expected and also triggers some other event or calls another API. read more to view What You Need to start API testing and also API Testing tools through the link below http://sharptester.com/2017/09/18/api-testing-api-test-tools/ |
Please OP i just got my company name approved online. I started the process myself. what do you suggest i do next . Also i think i need a lawyer also ? |
check |