I want to pull logs from the server, if the test ended up with FAILED status, tell me please what the signature of a function or fixture should look like, which will be called after each test and have information about its status.

I run the script like this

py.test -s -vv -l --alluredir allure / main.py

I have the below method:

PUBLIC methodname(WebDriver driver,formEntryMap<String,String>,String Colkey)
{
String Xpath = This will have the xpath of the input text box
inputfieldEntry(driver,Xpath,formEntryMap.get(ColKey));
}

This will read the value from the col

Feature file : Column | Value| SuceessNo | 1212 1414 |

Basically, the success 1212 and 1414 should be entered one below the other in the textbox so the input should be :

1212

1414

With the given method can someone give me inputs on how to "\n" in this method.

Put it as a child of the particular HTTP Request sampler - it will be applied to this sampler only.

More information:

• How to Use JMeter Assertions in Three Easy Steps
• JMeter Scoping Rules

I have a function that needs to do something like "try to move to node X in a directed graph", and my current implementation uses an indefinite loop like this

while(true) {    
    
    trySomething();    

    if (checkAreWeThereYet()) {
        break;
    }    

    if (inferInfiniteLoopIsHappening()) {
        throw;
    }
}

But with the current implementation I haven't found a way (yet) to actually trigger an infinite loop and test that last part (which I added in precisely because there was a bug in a previous iteration of the code that led to an infinite loop) to make sure it's working as intended.

I've been thinking of mocking some of the implementation details to fake "making a mistake" that would then lead to an infinite loop, but that strikes me as maybe not a best practice (?)

The only online resources I've been able to find so far around this are for the "simpler" but analogous "switch statement's default case is currently unreachable, but might be hit if a bug is introduced in upstream code" scenario, but I'm wondering if I've just been googling the wrong terms (?)

I'm trying to use the safaridriver but every time I try to enable it I get a segmentation fault. I already tried to restart my laptop but the problems stays.

admin@Bens-Air ~ % safaridriver --enable
Password:
zsh: segmentation fault  safaridriver --enable

Thankful for any help

I've created a basic test for checking if some article is displayed and I have a question regarding Page object model. In my solution, I've testing page, base page, map page with element id's, and method page with main logic. Test is something like - open site, navigate to articles, search for 'ArticleX', click on it, add it to the basket, edit the basket. For those operations, I've created 5 tests in my testing page, but now wondering is correct, or I should reduce them? All of them have repeated methods, which I test, for example the last test, called 'Edit basket'. I performing the following operations:

[Test]  
public void TestEditBasket() {  
    logicPage = new LogicPage();  
    logicPage.NavigateTo();
    logicPage.ClickArticles(); 
    logicPage.SearchArticleX();
    logicPage.PressArticleX();   
    logicPage.AddArticleXToBasket(); 
    logicPage.EditBasket(); 
//this test only checks name, quantity, price when you're editing basket

Assert.IsTrue(logicPage.ArticleNameInBasket.Text.Contains("ArticleXHeading"));

Assert.IsTrue(logicPage.ArticleQuantityInBasket.Text.Contains("1"));

Assert.IsTrue(logicPage.ArticlePriceInBasket.Text.Contains("$10"));

<p><code>NavigateTo</code>, <code>ClickArticles</code>, <code>SearchArticleX</code>, <code>PressArticleX</code>, <code>AddArticleXToBasket</code> are already tested in the previous tests, but I cannot go directly to the last step - <code>EditBasket</code>, that's why I'm using them in this test.
I can delete the other tests and left only this one. But will add around of 10 more asserts. Any advice?</p>

The answer depends on many other factors including the infrastructure.

1. Even POST requests can create unwanted changes in production DB so GET is mostly the only safe method, investigate if this is the case for your product.
2. Do you have a staging server where you do rest of the use cases (if you plan to use only POST and GET in production)
3. What is your team decision and what are their expectation
4. What is the product structure, is there test sandbox that you can access from the production environment so that you won't affect real users
5. What kind of product are you testing

So as in any test activity, the answer is:

1. The approach is context depended
2. You should have proper risk analysis on what happens if you don't test other http methods and stick to only http GET and POST
3. Is there a backup or restore option if something goes wrong.

Sometimes you won't be able to get answers for all those questions due to immature project stakeholders and process. In that case, I would stick to the below procedures:

1. Ensure to test all GET actions and validate the response schema
2. Check authentication and authorization test for test users. Make sure your test accounts have limited authorization and the test accounts have access only to test data. Don't test admin account use cases as it can cause unwanted changes
3. Don't use admin test accounts as account breaches can compromise the entire production environment
4. Check production environment response time
5. Run postman monitor to ensure health of the production API
6. Stay away from CRUD operations other than R (Read, means GET)
7. Discuss with the team on other use cases and be clear on the risk involved

The screenshot you provided is not a Testcase but a bug report.

You cannot consider a personal blog as final point of truth , it can be the authors mistake or a unnoticed mistake while uploading file to that web page.

Now coming to your actual question, there is no much difference between writing testcase in a Test Case management Tool and a Excel file. Excel is just another tool.

A tabular test case looks like :

This template was got from the same website ( https://www.softwaretestinghelp.com/test-case-template-examples/ )

There are both merits and demerits for every approach . Its hard to suggest merits and demerits unless you states the following things like :

1. What methodology you work in (Agile or waterfall ?)
2. What is your sprint length
3. How much time you gets for testing
4. What is your responsibility ( Is it only manual , is it automation or is it both)
5. What is the Team size
6. What is the release plan

But i would recommend following things as best practice

1. Adapt a TDD where you create test cases parallel to the development. So when the development sprint starts , start your test sprint in parallel and use the time to create the tabular testcases
2. Don't wait till you get the actual product to write the testcase and start testing it
3. Demand more time for documenting test case in tabular format if current sprint size is insufficient
4. First start with just writing down all the use cases that comes to your mind ( means just the title ) . Else you will feel the work tedious . First write down all use cases and once you are satisfied with the use cases you have decided, start writing the test steps and other details in tabular format
5. Split features between team members , give each team member the responsibility of testing a particular feature. This will give you more time to focus and document test scenarios for that specific feature than getting nervous about entire product.
6. Keep initial few days for test documentation , and start execution only after it is completely done. Don't do it in parallel else you lose focus while testing

Demerits:

1. If you are a single QA in a small sprint size team , this will be really hectic tasks and you might lose focus on actual testing and affect test quality
2. If you are single QA responsible for both automation and manual , then this will be a really waste of time and effort . It should be a complete no for this approach . Just copy paste the test script title if anyone really want to know what use cases are being tested . If they still insist demand more members into team

Please read : https://sqa.stackexchange.com/a/46008/40022 which explains a general recommendation of any type of documentation

First upload the file and click inspect , and see if you are able to see the input tag

If you see the input tag then:

you can create the input tag without triggering the click event by using javascript executor:

Eg: if the new element created after uploading the file is :

<form enctype="multipart/form-data" id="form-upload" ><input type="file" name="file" /></form>

Thenkn use below code:

body=driver.find_element_by_tag_name('body');

driver.execute_script("$(arguments[0]).prepend('<form enctype=\"multipart/form-data\" id=\"form-upload\" style=\"display: block;\"><input type=\"file\" name=\"file\" /></form>')", body);

Note:

I have set style=\"display: block;\" to make sure the input element is visible in UI for you make sure this script is valid. Once you are satisfied you can replace the block with 'none' as in your question. This time you cannot see the file after upload.

Set mouse coordinate as 0 using set option:

Auto It Set Option     'MouseCoordMode'    0
Auto It Set Option     'GUICoordMode'    0
Auto It Set Option     'PixelCoordMode'    0

https://www.autoitscript.com/wiki/AutoItSetOption

MouseCoordMode Sets the way coords are used in the mouse functions, either absolute coords or coords relative to the current active window:

0 = relative coords to the active window

1 = absolute screen coordinates (default)

2 = relative coords to the client area of the active window

+1 for View Results Tree. This ticks most of your boxes and each call will display green or red after running. If you want to put together a workflow diagram manually, you could use a free online editor like app.diagrams.net